[issue18022] Inconsistency between quopri.decodestring() and email.quoprimime.decode()

R. David Murray report at bugs.python.org
Mon Jun 10 00:51:15 CEST 2013


R. David Murray added the comment:

Most of the variations represent different invalid-input recovery choices.  I believe binascii's decoding of b'= \n' is incorrect, as is its decoding of b'==41'.  quopri's decoding of b'=\r' is arguably incorrect as well, given that python generally supports universal line ends.  Otherwise the decodings are all responses to erroneous input for which the behavior is not specified.

That said, we ought to pick one error recovery scheme and implement it in all places, and IMO it shouldn't be exactly any of the ones we've got.  Or better yet, use one common implementation.  Untangling quopri is on my (too large) List of Things To Do :)

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue18022>
_______________________________________


More information about the Python-bugs-list mailing list