Antoine Pitrou <pit...@free.fr> added the comment: > * Unicode objects are NUL-terminated, but only very external APIs > rely on this (e.g. code using the Windows Unicode API). Please > don't make the code in unicodeobject.c itself rely on this > subtle detail.
That's wishful thinking, don't you think? *I* am not making code in unicodeobject.c rely on this. It has been so for years, long before I was here. You should check who made that design decision in the first place instead of putting the blame on me. Besides, the fact that external APIs rely on it make it much more unchangeable than if it were an implementation detail. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8821> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
