Jay Freeman (saurik) <sau...@saurik.com> added the comment: Given that Python 3.x is still not ready for general use (and when this is discussed people make it quite clear that this is to be expected, and that a many year timeline was originally proposed for the Python 3.0 transition), it seems like this bug fix should have been backported to 2.x at some point in the last four years it has been open. :(
---------- nosy: +saurik _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue2481> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
