Message 107288 - 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.

In-reply-to
Author	vstinner
Recipients	doerwalter, eric.araujo, lemburg, loewis, pitrou, vstinner
Date	2010年06月07日.22:48:44
SpamBayes Score	0.42264482
Marked as misclassified	No
Message-id	<1275950926.09.0.370952171389.issue8838@psf.upfronthosting.co.za>

Content
MAL agreed to remove "t#" parsing format (#8839), whereas charbuffer_encode() main goal was to offer "t#" parsing format to Python object space. charbuffer_encode() is now useless in Python3. bytes() accepts any buffer object (read-only and read/write buffer), so readbuffer_encode() became useless in Python3. readbuffer_encode() and charbuffer_encode() were never documented, and are not used by any 3rd party library. Can we remove these two functions?

Content

MAL agreed to remove "t#" parsing format (#8839), whereas charbuffer_encode() main goal was to offer "t#" parsing format to Python object space. charbuffer_encode() is now useless in Python3. bytes() accepts any buffer object (read-only and read/write buffer), so readbuffer_encode() became useless in Python3.
readbuffer_encode() and charbuffer_encode() were never documented, and are not used by any 3rd party library.
Can we remove these two functions?

History
Date	User	Action	Args
2010年06月07日 22:48:46	vstinner	set	recipients: + vstinner, lemburg, loewis, doerwalter, pitrou, eric.araujo
2010年06月07日 22:48:46	vstinner	set	messageid: <1275950926.09.0.370952171389.issue8838@psf.upfronthosting.co.za>
2010年06月07日 22:48:44	vstinner	link	issue8838 messages
2010年06月07日 22:48:44	vstinner	create

homepage