[issue9200] Make str methods work with non-BMP chars on narrow builds

Ezio Melotti added the comment: I closed #12730 as a duplicate of this and updated the title of this issue. -- title: str.isprintable() is always False for large code points -> Make str methods work with non-BMP chars on narrow builds ___ Python tra

[issue9200] Make str methods work with non-BMP chars on narrow builds

Changes by Ezio Melotti : -- nosy: +tchrist ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue9200] Make str methods work with non-BMP chars on narrow builds

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue9200] Make str methods work with non-BMP chars on narrow builds

Ezio Melotti added the comment: The attached patch fixes all the str.is* methods and makes them work on narrow builds with non-BMP chars. It also includes the _Py_UNICODE_NEXT macro proposed in #10542. -- Added file: http://bugs.python.org/file22930/issue9200.diff __

[issue9200] Make str methods work with non-BMP chars on narrow builds

Ezio Melotti added the comment: (Note: I copied the macros from the other patch without changing the name. If the approach is good I'll get rid of the prefixes and separate the words in IS{HIGH|LOW}SURROGATE with an _.) -- ___ Python tracker

[issue9200] Make str methods work with non-BMP chars on narrow builds

Changes by Ezio Melotti : Removed file: http://bugs.python.org/file22930/issue9200.diff ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue9200] Make str methods work with non-BMP chars on narrow builds

Changes by Ezio Melotti : Added file: http://bugs.python.org/file22931/issue9200.diff ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue9200] Make str methods work with non-BMP chars on narrow builds

STINNER Victor added the comment: I don't think that macros specific to unicodeobject.c should get the _PY_UNICODE_ prefix. "_Py_" prefix is reserved to exported symbols, but symbols reserved for the Python interprefer itself. For _Py_UNICODE_NEXT, you can call it NEXT_CHARACTER(). _Py_UNICO

[issue9200] Make str methods work with non-BMP chars on narrow builds

Marc-Andre Lemburg added the comment: STINNER Victor wrote: > > STINNER Victor added the comment: > > I don't think that macros specific to unicodeobject.c should get the > _PY_UNICODE_ prefix. "_Py_" prefix is reserved to exported symbols, but > symbols reserved for the Python interprefer

[issue9200] Make str methods work with non-BMP chars on narrow builds

Ezio Melotti added the comment: Here's a new version of the patch. I decided to leave the prefix anyway, for consistency with what I'll commit to 3.3 and because without the prefix NEXT() looks ambiguous (and it's not entirely clear if it's private or not). I rewrote the macro as Victor sugges

[issue9200] Make str methods work with non-BMP chars on narrow builds

Changes by Ezio Melotti : -- assignee: belopolsky -> ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: