[issue38482] BUG in codecs.BufferedIncrementalDecoder
Jim Carroll
report at bugs.python.org
Tue Oct 15 07:59:23 EDT 2019
Jim Carroll <jim at carroll.com> added the comment:
According to the documentation (https://docs.python.org/3.7/library/codecs.html#codecs.iterdecode), the first parameter is a bytes object to decode (not an iterable of bytes). Which is also consistent with it's companion iterencode() which accepts a str object, not an iterable of chars.
Seems logical that one should be able to pass the output from iterencode() as the direct input to iterdecode() without having to convert, no?
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue38482>
_______________________________________
More information about the Python-bugs-list
mailing list