[issue10542] Py_UNICODE_NEXT and other macros for surrogates
report at bugs.python.org
Tue Aug 16 11:12:10 CEST 2011
Ezio Melotti <ezio.melotti at gmail.com> added the comment:
I think the 4 macros:
are quite straightforward and can avoid using the trailing _.
Since I would like to see #9200 fixed on 3.2 (and possibly 2.7 too), would it be ok to:
1) commit the patch with the trailing _ for all the macros on 3.2(/2.7);
2) commit the patch with the trailing _ only for the _NEXT macros in 3.3;
3) fix #9200 on all these branches using the new macros (with or without _);
4) remove the trailing _ from the _NEXT macros in 3.4 if it turns out to work well;
> we will still have to deal with surrogates in codecs,
> which is where these macros will get used
They will also be used in many str methods and afaiu PEP 393 should address that. I'm not sure it addresses codecs and builtin functions like chr() and ord() too.
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list