RetroSearch Browse

Thu Nov 3 23:21:24 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-November/114329.html

On 11/3/2011 5:43 PM, "Martin v. Löwis" wrote:

>> I had the impression that we were abolishing the wide versus narrow
>> build difference and that this issue would disappear. I must have missed
>> something.
>
> Most certainly. The Py_UNICODE type continues to exist for backwards
> compatibility. It is now always a typedef for wchar_t, which makes it
> a 16-bit type on Windows.

Thank you for answering: My revised impression now is that any string I 
create with Python code in Python 3.3+ (as distributed, without 
extensions or ctypes calls) will use the new implementation and will 
index and and slice correctly, even with extended chars. So indexing is 
only an issue for those writing or using C-coded extensions with the old 
unicode C-API on systems with a 16-bit wchar_t. Correct?

---
Terry Jan Reedy

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

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

[Python-Dev] Unicode exception indexing