martin at v.loewis.de martin at v.loewis.de
Wed Mar 7 12:39:51 CET 2012

• Previous message: [Python-Dev] PEP-393/PEP-3118: unicode format specifiers
• Next message: [Python-Dev] PEP-393/PEP-3118: unicode format specifiers
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

> 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

---

• Previous message: [Python-Dev] PEP-393/PEP-3118: unicode format specifiers
• Next message: [Python-Dev] PEP-393/PEP-3118: unicode format specifiers
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list