➜

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, gvanrossum, jcea, lemburg, loewis, ncoghlan, pconnell, petri.lehtinen, r.david.murray, ssbarnea, vstinner
Date 2013-04-23.21:46:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7fjxxncurZYbBgbs8njhBT6qwCQB9Uqv_t900h_hKzL3g@mail.gmail.com>
In-reply-to <1366745207.49.0.141431223703.issue7475@psf.upfronthosting.co.za>
Content 
No, transform/untransform as methods are a bad idea, but these *codecs*
should definitely come back.

The minimal change needed for that to be feasible is to give errors raised
during encoding and decoding more context information (at least the codec
name and error mode, and switching to the right kind of error).

MAL also stated on python-dev that codecs.encode and codecs.decode already
exist, so it should just be a matter of documenting them properly.
History
Date User Action Args
2013-04-23 21:46:42ncoghlansetrecipients: + ncoghlan, lemburg, gvanrossum, 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
2013-04-23 21:46:42ncoghlanlinkissue7475 messages
2013-04-23 21:46:42ncoghlancreate