➜

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 serhiy.storchaka
Recipients ezio.melotti, josh.r, serhiy.storchaka, vstinner, xiang.zhang
Date 2016-11-15.14:47:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1479221255.56.0.622488403343.issue21449@psf.upfronthosting.co.za>
In-reply-to
Content 
> Please don't modify _PyUnicode_FromId(), I prefer to keep it as it is, decode from UTF-8.

Then we should add handling of three special cases: PyUnicode_READY() fails, _PyUnicode_FromId() fails and both fail due to memory error. This means that should be implemented character-by-character encoding of UCS1, UCS2, UCS4 or wchar_t (with possible surrogate pairs) to UTF-8 and comparing with UTF-8 encoded data.
History
Date User Action Args
2016-11-15 14:47:35serhiy.storchakasetrecipients: + serhiy.storchaka, vstinner, ezio.melotti, josh.r, xiang.zhang
2016-11-15 14:47:35serhiy.storchakasetmessageid: <1479221255.56.0.622488403343.issue21449@psf.upfronthosting.co.za>
2016-11-15 14:47:35serhiy.storchakalinkissue21449 messages
2016-11-15 14:47:35serhiy.storchakacreate