A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2011-August/113080.html below:

[Python-Dev] PEP 393 review

[Python-Dev] PEP 393 review [Python-Dev] PEP 393 reviewVictor Stinner victor.stinner at haypocalc.com
Thu Aug 25 11:17:06 CEST 2011
Le 25/08/2011 06:46, Stefan Behnel a écrit :
>> Conversion to wchar_t* is common, especially on Windows.
>
> That's an issue. However, I cannot say how common this really is in
> practice. Surely depends on the specific code, right? How common is it
> in core CPython?

Quite all functions taking text as argument on Windows expects wchar_t* 
strings (UTF-16). In Python, we pass a "Py_UNICODE*" 
(PyUnicode_AS_UNICODE or PyUnicode_AsUnicode) because Py_UNICODE is 
wchar_t on Windows.

Victor
More information about the Python-Dev mailing list

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