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 vstinner
Date 2010-05-27.23:13:35
SpamBayes Score 0.18225257
Marked as misclassified No
Message-id <1275002017.75.0.302568685323.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. 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.
History
Date User Action Args
2010-05-27 23:13:38vstinnersetrecipients: + vstinner
2010-05-27 23:13:37vstinnersetmessageid: <1275002017.75.0.302568685323.issue8838@psf.upfronthosting.co.za>
2010-05-27 23:13:35vstinnerlinkissue8838 messages
2010-05-27 23:13:35vstinnercreate