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.
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