Gregory P. Smith <g...@krypto.org> added the comment:

Regardless, since things have already shipped in stable releases, there is a 
release that code _will_ encounter somewhere that does validate data but does 
not support overruling that behavior.  so i'm not sure if it actually matters 
to have this in 3.7 or 3.6 as anyone who wants to avoid complaints from users 
who happen to be on those python patch levels will need to include a workaround 
in their code or explicitly avoid those versions.

That said, PR 16321 looks overall like a good idea, I have no problem with it 
being backported to 3.7 and 3.6.

----------

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

Reply via email to