This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients belopolsky, ezio.melotti, georg.brandl, lemburg, mgiuca, pitrou, vstinner
Date 2010-12-29.23:59:19
SpamBayes Score 0.00010218069
Marked as misclassified No
Message-id <1293667162.36.0.732596443066.issue8821@psf.upfronthosting.co.za>
In-reply-to
Content
[MAL]
>  * 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.

I would like to note that several APIs have been introduced that require NUL-terminated unicode strings: Py_UNICODE_strlen(), Py_UNICODE_strcpy(), etc.  I see them used quite extensively in unicodeobject.c and elsewhere in Python codebase. Perhaps this train has left the station already.
History
Date User Action Args
2010-12-29 23:59:22belopolskysetrecipients: + belopolsky, lemburg, georg.brandl, pitrou, vstinner, ezio.melotti, mgiuca
2010-12-29 23:59:22belopolskysetmessageid: <1293667162.36.0.732596443066.issue8821@psf.upfronthosting.co.za>
2010-12-29 23:59:20belopolskylinkissue8821 messages
2010-12-29 23:59:19belopolskycreate