Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2002-May/024186.html below:

[Python-Dev] getting the UCS-2 representation of a unicode object

• Previous message: [Python-Dev] getting the UCS-2 representation of a unicode object
• Next message: [Python-Dev] getting the UCS-2 representation of a unicode object
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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

-- 
Marc-Andre Lemburg
CEO eGenix.com Software GmbH
______________________________________________________________________
Company & Consulting:                           http://www.egenix.com/
Python Software:                   http://www.egenix.com/files/python/

• Previous message: [Python-Dev] getting the UCS-2 representation of a unicode object
• Next message: [Python-Dev] getting the UCS-2 representation of a unicode object
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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