STINNER Victor <victor.stin...@haypocalc.com> added the comment:
r81854 removes codecs.charbuffer_encode() (and t# parsing format) from Python
3.2 (blocked in 3.1: r81855).
--
My problem with codecs.readbuffer_encode() is that it does accept byte *and*
character strings. If you want to get a byte string, just use bytes(input). If
you want to convert a character string to a byte string, use
input.encode("utf-8"). But accepting both types may lead to mojibake as we had
in Python2.
MAL> That's a common misunderstanding. The codec system does not
MAL> mandate a specific type combination. Only the helper methods
MAL> .encode() and .decode() on bytes and str objects in Python3 do.
This is related to #7475: we have to decide if we drop completly this
(currently unused) feature (eg. remove codecs.readbuffer_encode()), or if we
"reenable" this feature again (reintroduce hex, bz2, rot13, ... codecs). This
discussion should occur on the mailing list.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue8838>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
