Georg Brandl added the comment: > The main question: can be fix applied to 3.3 or it can wait for 3.4? > 3.2 has the same problem BTW.
I don't see any fix attached :) If it is a bug, it can be fixed before 3.3rc1, no need for release blocker status. ---------- priority: release blocker -> critical _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12623> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
