A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2018-May/153530.html below:

[Python-Dev] (Looking for) A Retrospective on the Move to Python 3

[Python-Dev] (Looking for) A Retrospective on the Move to Python 3 [Python-Dev] (Looking for) A Retrospective on the Move to Python 3Ethan Furman ethan at stoneleaf.us
Mon May 14 12:58:44 EDT 2018
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~
More information about the Python-Dev mailing list

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