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 r.david.murray
Recipients Jeremy.Hylton, barry, gvanrossum, r.david.murray, serhiy.storchaka
Date 2013-06-09.22:51:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1370818275.5.0.94082508417.issue18022@psf.upfronthosting.co.za>
In-reply-to
Content
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 :)
History
Date User Action Args
2013-06-09 22:51:15r.david.murraysetrecipients: + r.david.murray, gvanrossum, barry, Jeremy.Hylton, serhiy.storchaka
2013-06-09 22:51:15r.david.murraysetmessageid: <1370818275.5.0.94082508417.issue18022@psf.upfronthosting.co.za>
2013-06-09 22:51:15r.david.murraylinkissue18022 messages
2013-06-09 22:51:15r.david.murraycreate