➜

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, belopolsky, benjamin.peterson, cben, eric.araujo, ezio.melotti, flox, georg.brandl, gregory.p.smith, isoschiz, jcea, lemburg, loewis, ncoghlan, pconnell, petri.lehtinen, r.david.murray, ssbarnea, vstinner
Date 2013-11-10.09:25:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384075510.11.0.939352841182.issue7475@psf.upfronthosting.co.za>
In-reply-to
Content 
Issue 17823 is now closed, but not because it has been implemented. It turns out that the data driven nature of the incompatibility means it isn't really amenable to being detected and fixed automatically via 2to3.

Issue 19543 is a replacement proposal for the introduction of some additional codec related Py3k warnings in Python 2.7.7.
History
Date User Action Args
2013-11-10 09:25:10ncoghlansetrecipients: + ncoghlan, lemburg, loewis, barry, georg.brandl, gregory.p.smith, jcea, cben, belopolsky, vstinner, benjamin.peterson, ezio.melotti, eric.araujo, r.david.murray, ssbarnea, flox, petri.lehtinen, pconnell, isoschiz
2013-11-10 09:25:10ncoghlansetmessageid: <1384075510.11.0.939352841182.issue7475@psf.upfronthosting.co.za>
2013-11-10 09:25:10ncoghlanlinkissue7475 messages
2013-11-10 09:25:09ncoghlancreate