Message 106625 - Python tracker

➜

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	<[email protected]>
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.

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:38	vstinner	set	recipients: + vstinner
2010-05-27 23:13:37	vstinner	set	messageid: <[email protected]>
2010-05-27 23:13:35	vstinner	link	issue8838 messages
2010-05-27 23:13:35	vstinner	create