Mike Perry <m...@cogsmos.com> added the comment: Hello,
I am still able to reproduce this issue with Python 3.2.2. It seems as if this bug was closed with a the note: r70039 3.1 forward ported > 3.2 > default. Will be in 3.2.1. This leads me to believe that either 3.2.2 has a regression or the patch never made it into 3.2.1. Can anyone chime in with some more details? Thanks, Mike ---------- nosy: +Mike.Perry _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1028> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
