19/05/2002 10:52:27 PM, "Andreas Jung" <andreas@andreas-jung.com> wrote: > >Py_BuildValue() allows the usage of "u" or "u#" to convert UCS-2 >data into a Python unicode object, however Py_ParseTuple() converts >a unicode object to UTF-16. Is this an error in the documentation >or why is there a asymmmetry in the API? > I hope it is a doc problem. s/UCS-2/UTF-16/ UCS-2 is old hat. It is 16-bit-only, UTF-16 without the "surrogates" that allow representation of the whole 2**21 (possible) character set. BTW, isn't this a c.l.py question?
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