Nick Coghlan ncoghlan at gmail.com
Wed Mar 7 12:53:10 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 ]

---

On Wed, Mar 7, 2012 at 9:39 PM,  <martin at v.loewis.de> wrote:
> 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.

+1. It can go away at the same time that Py_UNICODE itself goes away.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

---

• 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