➜

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 benjamin.peterson, ezio.melotti, lemburg, ncoghlan, serhiy.storchaka, vstinner, xiang.zhang
Date 2016-10-13.05:50:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1476337812.57.0.551061582722.issue28426@psf.upfronthosting.co.za>
In-reply-to
Content 
Indeed. The only difference is that PyUnicode_AsDecodedUnicode fails for most encodings (except rot13), but PyUnicode_AsDecodedObject just crashes in debug build. It seems to me that these functions (as well as PyUnicode_AsEncodedUnicode) shouldn't exist it Python 3. None of these functions are documented. PyUnicode_AsDecodedObject emits Py3k warning in 2.7. PyUnicode_AsDecodedUnicode and PyUnicode_AsEncodedUnicode were added in Python 3 (2284fa89ab08), and the purpose of this is not clear to me. They work only with rot13, but general PyCodec_Decode and PyCodec_Encode can be used instead. Could you please explain Marc-André?
History
Date User Action Args
2016-10-13 05:50:12serhiy.storchakasetrecipients: + serhiy.storchaka, lemburg, ncoghlan, vstinner, benjamin.peterson, ezio.melotti, xiang.zhang
2016-10-13 05:50:12serhiy.storchakasetmessageid: <1476337812.57.0.551061582722.issue28426@psf.upfronthosting.co.za>
2016-10-13 05:50:12serhiy.storchakalinkissue28426 messages
2016-10-13 05:50:12serhiy.storchakacreate