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

Showing content from https://mail.python.org/pipermail/python-dev/2011-November/114426.html below:

[Python-Dev] unicode_internal codec and the PEP 393

• Previous message: [Python-Dev] unicode_internal codec and the PEP 393
• Next message: [Python-Dev] unicode_internal codec and the PEP 393
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> After a quick search on Google codesearch (before it disappears!), I don't 
> think that "encoding" a Unicode string to its internal PEP-393 representation 
> would satisfy any program. It looks like wchar_t* is a better candidate. 

Ok. Making it Py_UNICODE, documenting that, and deprecating the encoding
sounds fine to me as well.

Regards,
Martin

• Previous message: [Python-Dev] unicode_internal codec and the PEP 393
• Next message: [Python-Dev] unicode_internal codec and the PEP 393
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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