Daniel Diniz <aja...@gmail.com> added the comment: Rocky, No, 2.6 was released in 2008 and the bug was indeed filled against 2.5. However, 2.5 will not receive general bugfixes anymore, so I've changed the target version to 2.6 (as it's where it can be fixed if still present).
Setting it to pending so other people interested in this will have an incentive to verify whether it's fixed or not, so we can close or reopen. Thanks for your detailed analysis of the bug! ---------- status: open -> pending _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1531859> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
