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 vstinner
Recipients doerwalter, eric.araujo, lemburg, loewis, pitrou, vstinner
Date 2010-05-28.13:33:40
SpamBayes Score 0.0013023284
Marked as misclassified No
Message-id <1275053623.06.0.452501607935.issue8838@psf.upfronthosting.co.za>
In-reply-to
Content
> readbuffer_encode() and charbuffer_encode() are not really encoder 
> nor related to encodings: they are related to PyBuffer

That was the initial problem: codecs is specific to encodings (in Python3), encodes str to bytes, and decodes bytes (or any read buffer) to str.

I don't like readbuffer_*encode* and *charbuffer_encode*  function names, because there are different than other codecs: they encode *bytes* to bytes (and not str to bytes). I think that these functions should be removed or moved somewhere else under a different name.
History
Date User Action Args
2010-05-28 13:33:44vstinnersetrecipients: + vstinner, lemburg, loewis, doerwalter, pitrou, eric.araujo
2010-05-28 13:33:43vstinnersetmessageid: <1275053623.06.0.452501607935.issue8838@psf.upfronthosting.co.za>
2010-05-28 13:33:41vstinnerlinkissue8838 messages
2010-05-28 13:33:41vstinnercreate