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 barry, flavio, r.david.murray
Date 2014-11-27.19:08:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1417115299.53.0.300294560165.issue22666@psf.upfronthosting.co.za>
In-reply-to
Content
I'd have to double check, but I think having /r /n etc encoded in an encopded string is illegal per the rfcs.  It should be, anyway.  So IMO the bug is encoding them at all, but at this point we probably can't fix it for bacward compatibility reasons.

I'm leaving this issue open for the moment because I do want to check the rfc, and also double check what the new API does in this situation (and make sure there are tests).
History
Date User Action Args
2014-11-27 19:08:19r.david.murraysetrecipients: + r.david.murray, barry, flavio
2014-11-27 19:08:19r.david.murraysetmessageid: <1417115299.53.0.300294560165.issue22666@psf.upfronthosting.co.za>
2014-11-27 19:08:19r.david.murraylinkissue22666 messages
2014-11-27 19:08:19r.david.murraycreate