Mostly yes, but at least you could tell people to upgrade straight to 2.7.7 and skip 2.7.6.
2013/12/17 Donald Stufft <don...@stufft.io>: > Isn't changing it in 2.7.6 which is already released and then reverting in > 2.7.7 worse? Either way 2.7.6 will have this change and be in the wild and > broken for people who depend on it > >> On Dec 17, 2013, at 5:54 PM, Benjamin Peterson <benja...@python.org> wrote: >> >> 2013/12/17 Antoine Pitrou <solip...@pitrou.net>: >>> On Tue, 17 Dec 2013 13:18:25 -0500 >>> Tres Seaver <tsea...@palladion.com> wrote: >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA1 >>>> >>>> http://hg.python.org/cpython/rev/b1e94e332ec8 >>>> >>>> >>>> Do we really want to change an undocumented-but-effectively-public API in >>>> a late-in-the-release-cycle third dot release? It caused, ZODB's tests >>>> to fail, for instance. >>> >>> Given the change doesn't seem to bring any visible change for users >>> (either performance or robustness), I think it would be safe to revert >>> it *in 2.7*. >> >> I agree with Antoine. It's better not to break even morally-broken >> programs like the zope tests in 2.7.x if it doesn't win anything. >> >> >> -- >> Regards, >> Benjamin >> _______________________________________________ >> Python-Dev mailing list >> Python-Dev@python.org >> https://mail.python.org/mailman/listinfo/python-dev >> Unsubscribe: >> https://mail.python.org/mailman/options/python-dev/donald%40stufft.io -- Regards, Benjamin _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
