[Python-Dev] (Looking for) A Retrospective on the Move to Python 3 (original) (raw)
Wes Turner wes.turner at gmail.com
Mon May 14 13:36:34 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 Monday, May 14, 2018, Ethan Furman <ethan at stoneleaf.us> wrote:
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.
https://github.com/python/cpython/blame/master/Lib/future.py
--
Ethan
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/wes. turner%40gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180514/3f477702/attachment.html>
- 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 ]