Marc-Andre Lemburg <m...@egenix.com> added the comment: Benjamin Peterson wrote: > > Benjamin Peterson <benja...@python.org> added the comment: > > 2009/12/11 Marc-Andre Lemburg <rep...@bugs.python.org>: >> 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7475> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
