Greg Ewing, 26.06.2010 09:58: > Tres Seaver wrote: > >> I do know for a fact that using a UCS2-compiled Python instead of the >> system's UCS4-compiled Python leads to measurable, noticable drop in >> memory consumption of long-running webserver processes using Unicode > > 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. Stefan
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