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 lemburg, vstinner
Date 2010-05-28.07:54:16
SpamBayes Score 0.097665
Marked as misclassified No
Message-id <>
In-reply-to <>
STINNER Victor wrote:
> New submission from STINNER Victor <>:
> readbuffer_encode() and charbuffer_encode() are not really encoder nor related to encodings: they are related to PyBuffer. readbuffer_encode() uses "s#" format and charbuffer_encode() uses "t#" format to parse their arguments. Both functions were introduced by the creation of the _codecs module 10 years ago (r14660).
> I think that these functions should be removed. memoryview() should be used instead.
> Note: charbuffer_encode() is the last function using on of the "t" format (t, t#, t*) in Python3.

Those two encoder functions were meant to be used by Python codec
implementations which want to use the readbuffer and charbuffer
interfaces available in Python via "s#" and "t#" to access input
object data.

They are not used by the builtin codecs, but may well be in use
by 3rd party codecs.

I'm not sure why you think those functions are not encoders.
Date User Action Args
2010-05-28 07:54:19lemburgsetrecipients: + lemburg, vstinner
2010-05-28 07:54:17lemburglinkissue8838 messages
2010-05-28 07:54:16lemburgcreate