RetroSearch Browse

Fri Apr 14 11:18:44 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-April/063736.html

M.-A. Lemburg wrote:
> I'd argue that such code is broken anyway: 3rd party code simply
> cannot make any assumptions on the typedef behind Py_UNICODE.

The code would work just fine now, but will stop working with the
change. Users of the code might not be open to arguments.

In any case, it's up to the release manager to decide.

> Note that you'd only see this change when compiling Python in the
> non-standard UCS4 setting on Linux.

Sure. That happens to be the default on many Linux distributions,
though.

Regards,
Martin

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

Showing content from https://mail.python.org/pipermail/python-dev/2006-April/063736.html below:

[Python-Dev] unicode vs buffer (array) design issue can crash interpreter