R. David Murray added the comment:
You have to ship one of them by ("one of them" being either the fix or the
backout) in 3.5.0, Larry, otherwise you are introducing a security
vulnerability into 3.5 that doesn't exist in 3.4. If you don't ship it in rc3,
then there's no chance that 3.5.0 will be unchanged from rc3, which is the
ideal we should be aiming for (that's why it's called a "release *candidate*").
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25005>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
