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/2012-February/116885.html below:

[Python-Dev] PEP 414

[Python-Dev] PEP 414 [Python-Dev] PEP 414Barry Warsaw barry at python.org
Sun Feb 26 18:31:18 CET 2012
This seems like too strong a statement:

    "Python 2.6 and Python 2.7 support syntax features from Python 3 which for
    the most part make a unified code base possible. Many thought that the
    unicode_literals future import might make a common source possible, but it
    turns out that it's doing more harm than good."

While it may be true for *some* problem domains, such as WSGI apps, it is not
true in general, IMO.  I use this future import all the time in both libraries
and applications and it's almost always helpful.

Cheers,
-Barry

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