Ian Cordasco added the comment:

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.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue19494>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to