Mitchell Model <m...@acm.org> added the comment: Thanks for letting me know (and with a personalized message, yet!). I wasn't paying attention -- i verified that the problem exists in 2.7 and 3.1 and I just dragged 3.1 down to 2.6. Although I've been working furiously in Python for the past six months, I haven't been writing or teaching so I haven't been combing the documentation or testing examples or using obscure or forgotten features, which together are the source of nearly all my bug reports. So I just automatically did what I used to do. I understand the issue and difference; I just didn't realize 2.6 was closed -- I didn't really mean that this should be fixed in anything other than the current or even next release of anything. On Dec 24, 2010, at 3:36 PM, Terry J. Reedy wrote:
> > Terry J. Reedy <tjre...@udel.edu> added the comment: > > Mitchell: 2.6 is closed to revision except for security issues > > ---------- > nosy: +terry.reedy > resolution: wont fix -> > versions: +Python 3.2 -Python 2.6 > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <http://bugs.python.org/issue10733> > _______________________________________ ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10733> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
