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 martin.panter
Recipients doerwalter, ezio.melotti, lemburg, martin.panter, serhiy.storchaka, vstinner
Date 2016-08-19.09:06:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content
Serhiy’s two proposals won’t work for codecs that include non-zero output for zero input:

>>> tuple(iterencode((), "utf-8-sig"))
(b'\xef\xbb\xbf',)
>>> encode(b"", "uu")
b'begin 666 <data>\n \nend\n'
>>> encode(b"", "zlib")
b'x\x9c\x03\x00\x00\x00\x00\x01'

However I agree that changing the incremental codec APIs is not ideal. Since nobody seems to care that much, it might be simpler to document that:

* iterencode() only works where text str objects can be encoded, so base64-codec is not supported, but rot13-codec is supported
* iterdecode() only works where bytes objects can be decoded, so rot13-codec is not supported, but base64-codec should be supported (pending other aspects of Issue 20132)
History
Date User Action Args
2016-08-19 09:06:31martin.pantersetrecipients: + martin.panter, lemburg, doerwalter, vstinner, ezio.melotti, serhiy.storchaka
2016-08-19 09:06:30martin.pantersetmessageid: <[email protected]>
2016-08-19 09:06:30martin.panterlinkissue23231 messages
2016-08-19 09:06:30martin.pantercreate