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/2010-June/101144.html below:

[Python-Dev] thoughts on the bytes/string discussion

[Python-Dev] thoughts on the bytes/string discussion [Python-Dev] thoughts on the bytes/string discussionEric Smith eric at trueblade.com
Sun Jun 27 12:53:00 CEST 2010
On 6/27/2010 5:48 AM, Greg Ewing wrote:
> Stefan Behnel wrote:
>> Greg Ewing, 26.06.2010 09:58:
>>
>>> Would there be any sanity in having an option to compile
>>> Python with UTF-8 as the internal string representation?
>>
>> It would break Py_UNICODE, because the internal size of a unicode
>> character would no longer be fixed.
>
> It's not fixed anyway with the 2-char build -- some
> characters are represented using a pair of surrogates.
>

But isn't this currently ignored everywhere in python's code?

Eric.

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