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, ezio.melotti, r.david.murray, scharron, terry.reedy, vstinner
Date 2014-08-23.02:44:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1408761867.6.0.597116110495.issue22232@psf.upfronthosting.co.za>
In-reply-to
Content
See issue 7643 for some technical background.  There are some other interesting issues to read if you seach the tracker for 'splitlines unicode', one of which is an open doc issue. Clearly the docs about this are inadequate.

Basically, though, I think you are correct.  email should not be using splitlines().  It was more or less correct when email was splitting binary data, but even then it wasn't exactly correct per the letter of RFC.

Unfortunately not using splitlines has some performance implications...but then again we haven't done any sort of performance improvement pass on the new email code, so it may well be marginal in the overall scheme of things.
History
Date User Action Args
2014-08-23 02:44:27r.david.murraysetrecipients: + r.david.murray, barry, terry.reedy, vstinner, ezio.melotti, scharron
2014-08-23 02:44:27r.david.murraysetmessageid: <1408761867.6.0.597116110495.issue22232@psf.upfronthosting.co.za>
2014-08-23 02:44:27r.david.murraylinkissue22232 messages
2014-08-23 02:44:27r.david.murraycreate