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 ncoghlan
Recipients barry, bkabrda, martin.panter, ncoghlan, petr.viktorin, rkuska
Date 2015-02-17.02:09:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1424138983.24.0.934950398701.issue22555@psf.upfronthosting.co.za>
In-reply-to
Content
Slavek et al - you folks may be interested in this one, as it tracks several issues that I consider relevant to the Python 2 -> 3 migration effort.

Redoing the list in a way that should render the strike-throughs for closed issues:

* Improved Windows console Unicode support (see
https://pypi.python.org/pypi/win_unicode_console for details)
* Changing the encoding and error handling of an existing stream
(issue 15216)
* Allowing "backslashreplace" to be used on input (issue 22286)
* Adding "codecs.convert_surrogates" (issue 18814)
* Adding "wsgiref.util.dump_wsgistr" and "wsgiref.util.load_wsgistr" (issue 22264)
* Adding "bytes.hex", "bytearray.hex" and "memoryview.hex" (issue 9951)
* Adding a binary data formatting mini-language (depends on issue 9951, likely needs to be escalated to a full PEP for design discussion visibility) (issue 22385)
History
Date User Action Args
2015-02-17 02:09:43ncoghlansetrecipients: + ncoghlan, barry, petr.viktorin, martin.panter, bkabrda, rkuska
2015-02-17 02:09:43ncoghlansetmessageid: <1424138983.24.0.934950398701.issue22555@psf.upfronthosting.co.za>
2015-02-17 02:09:43ncoghlanlinkissue22555 messages
2015-02-17 02:09:41ncoghlancreate