RetroSearch Browse

Wed Mar 7 12:39:51 CET 2012 · https://mail.python.org/pipermail/python-dev/2012-March/117390.html

> The main reason why I raised the issue is this: If Python-3.3 is shipped
> with 'u' -> UCS4 in the array module and *then* someone figures out that
> the above format codes are a great idea, we'd be stuck with yet another
> format code incompatibility.

Ah. I think the array module should maintain compatibility with Python 3.2,
i.e. "u" should continue to denote Py_UNICODE, i.e. 7fa098f6dc6a should be
reverted.

It may be that the 'u' code is not particularly useful, but AFAICT, it never
was useful.

Regards,
Martin

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

Showing content from https://mail.python.org/pipermail/python-dev/2012-March/117390.html below:

[Python-Dev] PEP-393/PEP-3118: unicode format specifiers