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

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

[Python-Dev] unicode/string asymmetries

• Previous message: [Python-Dev] unicode/string asymmetries
• Next message: [Python-Dev] unicode/string asymmetries
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Martin:

> Unfortunately, that is quite difficult. Python does not guarantee that
> the internal representation of Unicode strings uses wchar_t, so such a
> conversion definitely requires explicit memory management.

   This could be a problem with my file patches as I have been using
PyUnicode_AS_UNICODE which will 4 byte strings if Py_UNICODE_WIDE is
defined. 4 byte strings can not be passed to the Windows API. So it looks
like PyUnicode_AsWideChar has to be used instead with a wrapper to allocate
enough memory to hold the resulting string.

   Neil

• Previous message: [Python-Dev] unicode/string asymmetries
• Next message: [Python-Dev] unicode/string asymmetries
• 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