➜

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, larry, lemburg, ncoghlan, serhiy.storchaka, vstinner, xiang.zhang
Date 2016-10-13.09:59:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1476352795.11.0.833566804993.issue28426@psf.upfronthosting.co.za>
In-reply-to
Content 
I propose following:

1) Fix a crash in PyUnicode_AsDecodedObject by removing unicode_result() in all maintained 3.x versions (starting from 3.4? or 3.3?).

2) Deprecate PyUnicode_AsDecodedObject, PyUnicode_AsDecodedUnicode and PyUnicode_AsEncodedUnicode in 3.6, make they always failing in 3.7 and remove them in future versions. They shouldn't be widely used since they are not documented, PyUnicode_AsDecodedObject already is deprecated in 2.7, and the only supported standard encoding is rot13.
History
Date User Action Args
2016-10-13 09:59:55serhiy.storchakasetrecipients: + serhiy.storchaka, lemburg, ncoghlan, vstinner, larry, benjamin.peterson, ezio.melotti, xiang.zhang
2016-10-13 09:59:55serhiy.storchakasetmessageid: <1476352795.11.0.833566804993.issue28426@psf.upfronthosting.co.za>
2016-10-13 09:59:54serhiy.storchakalinkissue28426 messages
2016-10-13 09:59:54serhiy.storchakacreate