On Sat, Dec 17, 2016 at 8:07 AM, Ethan Furman <ethan at stoneleaf.us> wrote: > On 12/16/2016 11:24 AM, Guido van Rossum wrote: > >> I am beginning to think that `from __future__ import unicode_literals` >> does >> more harm than good. I don't recall exactly why we introduced it, but >> with >> the restoration of u"" literals in Python 3.3 we have a much better story >> for writing straddling code that is unicode-correct. > > > So cross-version code would be primarily 2.7 and 3.3+ ? I can live with > that. Or 3.5+ so you get percent formatting for bytes. +1 for deprecating unicode_literals; I don't remember ever using or wanting it. ChrisA
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4