RetroSearch Browse

Sat May 7 01:45:24 CEST 2005 · https://mail.python.org/pipermail/python-dev/2005-May/053494.html

Nicholas Bastin wrote:
> Because the encoding of that buffer appears to be different depending on
> the configure options.

What makes it appear so? sizeof(Py_UNICODE) changes when you change
the option - does that, in your mind, mean that the encoding changes?

> If that isn't true, then someone needs to change
> the doc, and the configure options.  Right now, it seems *very* clear
> that Py_UNICODE may either be UCS-2 or UCS-4 encoded if you read the
> configure help, and you can't use the buffer directly if the encoding is
> variable.  However, you seem to be saying that this isn't true.

It's a compile-time option (as all configure options). So at run-time,
it isn't variable.

Regards,
Martin

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

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

[Python-Dev] New Py_UNICODE doc