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 flox, lemburg, loewis, skip.montanaro
Date 2009-12-10.23:25:02
SpamBayes Score 1.2161745e-06
Marked as misclassified No
Message-id <4B21834D.9070601@egenix.com>
In-reply-to <1260486915.31.0.572111759191.issue7475@psf.upfronthosting.co.za>
Content
Martin v. Löwis wrote:
> 
> Martin v. Löwis <martin@v.loewis.de> added the comment:
> 
> These are not encodings, in that they don't convert characters to bytes.
> It was a mistake that they were integrated into the codecs interfaces in
> Python 2.x; this mistake is corrected in 3.x.

Martin, I beg your pardon, but these codecs indeed implement valid
encodings and the fact that these codecs were removed was a
mistake.

They should be readded to Python 3.x.

Note that just because a codec doesn't convert between bytes
and characters only, doesn't make it wrong in any way. The codec
architecture in Python is designed to support same type encodings
just as well as ones between bytes and characters.
History
Date User Action Args
2009-12-10 23:25:04lemburgsetrecipients: + lemburg, loewis, skip.montanaro, flox
2009-12-10 23:25:03lemburglinkissue7475 messages
2009-12-10 23:25:03lemburgcreate