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 icordasc
Recipients Rosuav, arigo, christian.heimes, demian.brecht, icordasc, mcepl, ncoghlan, orsenthil, pitrou, r.david.murray
Date 2014-10-10.00:24:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
This behaviour is allowed by the RFC but not encouraged. There's a difference between MUST, SHOULD, and MAY

Sending this pre-emptively could well cause unexpected errors for users. Changing the default even in 3.5 will make writing compatible code difficult because you'll have substantially different behaviour.

Regardless of whether we add this to 2.7 or not, it should be an entirely separate class. I personally feel this isn't a bug fix but a feature addition for 2.7 so I'm -0.5 on adding it there. It's also not a security backport so it doesn't fit into PEP 466.
Date User Action Args
2014-10-10 00:24:16icordascsetrecipients: + icordasc, arigo, ncoghlan, orsenthil, pitrou, christian.heimes, mcepl, r.david.murray, Rosuav, demian.brecht
2014-10-10 00:24:16icordascsetmessageid: <>
2014-10-10 00:24:16icordasclinkissue19494 messages
2014-10-10 00:24:15icordasccreate