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-03.08:46:28
SpamBayes Score 8.162485e-08
Marked as misclassified No
Message-id <>
In-reply-to <>
Alexander Belopolsky wrote:
> Alexander Belopolsky <> added the comment:
> I am probably a bit late to this discussion, but why these things should be called "codecs" and why should they share the registry with the encodings?  It looks like the proper term would be "transformations" or "transforms".

.transform() is just the name of the method. The codecs are still just
that: codecs, i.e. objects that encode and decode data. The types they
support are defined by the codecs, not by the helper methods.

In Python3, the str and bytes methods .encode() and .decode() will
only support str->bytes->str conversions. The new
str and bytes .transform() method adds back str->str and

The codec subsystem does not impose restrictions on the type combinations
a codec can support, and that's per design.
Date User Action Args
2010-12-03 08:46:30lemburgsetrecipients: + lemburg, loewis, georg.brandl, belopolsky, vstinner, benjamin.peterson, eric.araujo, ssbarnea, flox
2010-12-03 08:46:28lemburglinkissue7475 messages
2010-12-03 08:46:28lemburgcreate