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/2005-May/053489.html below:

[Python-Dev] New Py_UNICODE doc

[Python-Dev] New Py_UNICODE doc [Python-Dev] New Py_UNICODE doc"Martin v. Löwis" martin at v.loewis.de
Sat May 7 01:35:08 CEST 2005
Nicholas Bastin wrote:
> The important piece of information is that it is not guaranteed to be a
> particular one of those sizes.  Once you can't guarantee the size, no
> one really cares what size it is.

Please trust many years of experience: This is just not true. People
do care, and they want to know. If we tell them "it depends", they
ask "how can I find out".

> The documentation should discourage
> developers from attempting to manipulate Py_UNICODE directly, which,
> other than trivia, is the only reason why someone would care what size
> the internal representation is.

Why is that? Of *course* people will have to manipulate Py_UNICODE*
buffers directly. What else can they use?

Regards,
Martin
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