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 benjamin.peterson, flox, georg.brandl, lemburg, loewis, skip.montanaro
Date 2009-12-11.13:13:49
SpamBayes Score 5.73272e-08
Marked as misclassified No
Message-id <>
In-reply-to <>
Benjamin Peterson wrote:
> Benjamin Peterson <> added the comment:
> 2009/12/11 Marc-Andre Lemburg <>:
>> codecs.encode()/.decode() provide access to all codecs, regardless
>> of their supported type combinations and of course, you can use
>> them directly via the codec registry, subclass from them, etc.
> Didn't you have a proposal for bytes.transform/untransform for
> operations like this?

Yes. At the time it was postponed, since I brought it up late
in the 3.0 release process. Perhaps I should bring it up again.

Note that those methods are just convenient helpers to access
the codecs and as such only provide limited functionality.

The full machinery itself is accessible via the codecs module and
the code in the encodings package. Any decision to include a codec
or not needs to be based on whether it fits the framework in those
modules/packages, not the functionality we expose on unicode and
bytes objects.
Date User Action Args
2009-12-11 13:13:51lemburgsetrecipients: + lemburg, loewis, skip.montanaro, georg.brandl, benjamin.peterson, flox
2009-12-11 13:13:50lemburglinkissue7475 messages
2009-12-11 13:13:50lemburgcreate