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 Lukasa, barry, demian.brecht, icordasc, martin.panter, mgdelmonte, orsenthil, piotr.dobrogost, r.david.murray
Date 2016-09-09.22:23:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I guess we could add this secret policy flag that the email parser checks. The solution should still be applied as a bug fix to 3.5 as well as 3.6+. I would have to make the flag “very” unique, to reduce the chance of it breaking user code. I.e. adding policy._strict_end_of_headers might interfere with somebody’s user-defined policy class, but maybe policy.__strict_end_of_headers__ is safe, since user code is not supposed to invent such attribute names. Or do you think it “_strict_end_of_headers” name is fair game since the policy stuff is/was provisional?

It would be good to fix 2.7. This bug, and the duplicate report, were both originally reported for 2.7. I haven’t looked at the situation there in detail, but it looks completely different. HTTPMessage is based on the “mimetools” package, and there is a lot more parsing code already in “httplib”.
Date User Action Args
2016-09-09 22:23:28martin.pantersetrecipients: + martin.panter, barry, orsenthil, r.david.murray, piotr.dobrogost, icordasc, demian.brecht, Lukasa, mgdelmonte
2016-09-09 22:23:28martin.pantersetmessageid: <>
2016-09-09 22:23:28martin.panterlinkissue24363 messages
2016-09-09 22:23:28martin.pantercreate