[issue10542] Py_UNICODE_NEXT and other macros for surrogates
report at bugs.python.org
Thu Dec 30 12:14:53 CET 2010
Georg Brandl <georg at python.org> added the comment:
> I think the proposal is that fixing this minefield can wait until
> Python 3.3 (or even 3.4, or later).
That is what I was thinking. (Alex: You might not know that Martin
was the main proponent of non-ASCII identifiers, so this assessment
should have some weight.)
> I'm thinking about an approach of a variable representation:
> one, two, or four bytes, depending on the widest character that
> appears in the string. I think it can be arranged to make this mostly
> backwards-compatible with existing APIs, so it doesn't need to wait
> for py4k, IMO. OTOH, I'm not sure I'll make it for 3.3.
That is an interesting idea. I would be interested in helping out
when you'll implement it.
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list