19/05/2002 11:25:26 PM, "M.-A. Lemburg" <mal@lemburg.com> wrote: >Andreas Jung 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? > >Sounds like a documentation bug: it should be UCS-2 since that's >what's used as internal data represenation in narrow Unicode >builds (the default). > I sincerely hope that you are mistaken in your belief that UCS-2 is so used.
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