"Martin v. Löwis" martin at v.loewis.de
Wed Nov 9 23:45:16 CET 2011

• Previous message: [Python-Dev] unicode_internal codec and the PEP 393
• Next message: [Python-Dev] unicode_internal codec and the PEP 393
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

> After a quick search on Google codesearch (before it disappears!), I don't 
> think that "encoding" a Unicode string to its internal PEP-393 representation 
> would satisfy any program. It looks like wchar_t* is a better candidate. 

Ok. Making it Py_UNICODE, documenting that, and deprecating the encoding
sounds fine to me as well.

Regards,
Martin

---

• Previous message: [Python-Dev] unicode_internal codec and the PEP 393
• Next message: [Python-Dev] unicode_internal codec and the PEP 393
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list