Martin v. Löwis added the comment: > It's a blocker because the fix broke a couple of tests.
That cannot possibly be the explanation why haypo declared it a blocker on 2012-08-01; the fix was only applied on 2012-08-04. But I agree that it should block the release now; hence I propose to roll back the entire set of changes and revert to the 3.2 state. > And it's also a regression from 3.1 and 2.7. Since 3.2 was released with this behavior, this bug cannot manage to block 3.3. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13119> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
