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 belopolsky, benjamin.peterson, eric.araujo, flox, georg.brandl, lemburg, loewis, ssbarnea, vstinner
Date 2010-12-06.11:49:37
SpamBayes Score 1.7272313e-06
Marked as misclassified No
Message-id <4CFCCDD0.5080409@egenix.com>
In-reply-to <1291575884.94.0.398471521067.issue7475@psf.upfronthosting.co.za>
Content
Martin v. Löwis wrote:
> 
> Martin v. Löwis <martin@v.loewis.de> added the comment:
> 
> As per 
> 
> http://mail.python.org/pipermail/python-dev/2010-December/106374.html
> 
> I think this checkin should be reverted, as it's breaking the language moratorium.

I've asked Guido. We may have to revert the addition of the new
methods and then readd them for 3.3, but I don't really see
them as difficult to implement for the other Python implementations,
since they are just interfaces to the codec sub-system.

The readdition of the codecs and changes to support them in the
codec system do not fall under the moratorium, since they are
stdlib changes.
History
Date User Action Args
2010-12-06 11:49:45lemburgsetrecipients: + lemburg, loewis, georg.brandl, belopolsky, vstinner, benjamin.peterson, eric.araujo, ssbarnea, flox
2010-12-06 11:49:37lemburglinkissue7475 messages
2010-12-06 11:49:37lemburgcreate