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 pitrou
Recipients lemburg, loewis, pitrou, vstinner
Date 2010-05-28.12:19:19
SpamBayes Score 0.0196864
Marked as misclassified No
Message-id <>
> Any Python object can expose a buffer interface and the above
> functions then allow accessing these interfaces from within
> Python.

What's the point? The codecs functions already support objects exposing the buffer interface:

>>> b = b"\xe9"
>>> codecs.latin_1_decode(memoryview(b))
('é', 1)
>>> codecs.latin_1_decode(array.array("b", b))
('é', 1)

Those two functions are undocumented. They serve no useful purpose (you can call the bytes(...) constructor instead, or even use the buffer object directly as showed above). They are badly named since they don't have anything to do with codecs. Google Code Search shows them not appearing anywhere else than implementations of the Python stdlib. Removing them only seems reasonable.
Date User Action Args
2010-05-28 12:19:21pitrousetrecipients: + pitrou, lemburg, loewis, vstinner
2010-05-28 12:19:21pitrousetmessageid: <>
2010-05-28 12:19:19pitroulinkissue8838 messages
2010-05-28 12:19:19pitroucreate