[Python-Dev] (Looking for) A Retrospective on the Move to Python 3 (original) (raw)
Chris Barker - NOAA Federal chris.barker at noaa.gov
Mon May 14 18:33:14 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 ]
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?
You'll need to be more specific. future has been around for a looooong time.
I meant the various ones that support py2/3 compatibility — I know division predates py3, not sure about the others.
But it was a rhetorical question anyway :-) -CHB
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
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/chris.barker%40noaa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180514/9df17fb8/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 ]