➜

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 lemburg
Recipients docs@python, eamanu, lemburg, serhiy.storchaka, terry.reedy, vstinner
Date 2019-01-05.21:30:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1546723851.82.0.775265565403.issue35616@roundup.psfhosted.org>
In-reply-to
Content 
Why not change the wording to read "... will be considered for removal in the next major Python release".

Note that removal of Py_UNICODE APIs will not only break compatibility with Python 2, but also with the early Python 3 releases.

And please also consider that we may see another change in the Unicode implementation... I've heard discussions about using UTF-8 as internal representation to address the issues with the current unified approach.
History
Date User Action Args
2019-01-05 21:30:53lemburgsetrecipients: + lemburg, terry.reedy, vstinner, docs@python, serhiy.storchaka, eamanu
2019-01-05 21:30:51lemburgsetmessageid: <1546723851.82.0.775265565403.issue35616@roundup.psfhosted.org>
2019-01-05 21:30:51lemburglinkissue35616 messages
2019-01-05 21:30:51lemburgcreate