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/117104.html below:

[Python-Dev] PEP 414 - Unicode Literals for Python 3

[Python-Dev] PEP 414 - Unicode Literals for Python 3 [Python-Dev] PEP 414 - Unicode Literals for Python 3Lennart Regebro regebro at gmail.com
Wed Feb 29 07:35:55 CET 2012
On Tue, Feb 28, 2012 at 16:39, Vinay Sajip <vinay_sajip at yahoo.co.uk> wrote:
> Serhiy Storchaka <storchaka <at> gmail.com> writes:
>
>> Another pertinent question: "What are disadvantages of PEP 414 is adopted?"
>
> It's moot, but as I see it: the purpose of PEP 414 is to facilitate a single
> codebase across 2.x and 3.x.

The bytes/native/unicode issue is an issue even if you use 2to3. But
of course that *is* a form of "single codebase" so maybe that's what
you meant. :-)

//Lennart
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