[Python-Dev] (Looking for) A Retrospective on the Move to Python 3
Ethan Furman
ethan at stoneleaf.us
Mon May 14 12:58:44 EDT 2018
More information about the Python-Dev mailing list
Mon May 14 12:58:44 EDT 2018
- Previous message (by thread): [Python-Dev] (Looking for) A Retrospective on the Move to Python 3
- Next message (by thread): [Python-Dev] (Looking for) A Retrospective on the Move to Python 3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 05/14/2018 09:34 AM, Chris Barker via Python-Dev wrote: > between 3.0 and 3.6 (.5?) -- py3 grew a lot of minor features that made it easier to write py2/py3 compatible code. > u"string", b'bytes %i' % something -- and when where the various __future__ imports made available? > > If these had been in place in 3.0, the whole process would have been easier :-( You'll need to be more specific. __future__ has been around for a looooong time. -- ~Ethan~
- Previous message (by thread): [Python-Dev] (Looking for) A Retrospective on the Move to Python 3
- Next message (by thread): [Python-Dev] (Looking for) A Retrospective on the Move to Python 3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list