Jason R. Coombs <jar...@jaraco.com> added the comment:

> I'm not against that concept, but it is only appropriate for >= 3.9 as that'd 
> be adding a feature.  This issue is marked a release blocker to decide what 
> to do for 3.5-3.7 (and maybe 3.8 if deemed a serious breaking change).

The key part of the regression for 2.7 and 3.5+ was that it became impractical 
to retain the existing behavior of sending invalid bytes. My recommendation is 
to provide a mechanism to achieve compatibility with the older versions of 
Python. Although it's a "feature", it's also a feature necessitated by the 
security bugfix and to alleviate the regression. For this reason, I think the 
change should be applied to all Python versions that were patched for the 
security issue.

----------

_______________________________________
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