This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients Arfrever, ezio.melotti, gvanrossum, lemburg, loewis, mrabarnett, pitrou, tchrist, terry.reedy
Date 2011-08-26.21:04:03
SpamBayes Score 0.00023005596
Marked as misclassified No
Message-id <1314392644.0.0.971823116704.issue12728@psf.upfronthosting.co.za>
In-reply-to
Content
This bug could do with a little less attitude.  That said, I think it is a bug and should be fixed, at the very least for Python 3.3.  As always, it is a matter of much debate to what extent bugs can be fixed in previous Python versions (specifically, 2.7 and 3.2) without breaking more code than it fixes, and I don't want to jump the gun on that issue.  Let's first see what it takes to fix this for 3.3.
History
Date User Action Args
2011-08-26 21:04:04gvanrossumsetrecipients: + gvanrossum, lemburg, loewis, terry.reedy, pitrou, ezio.melotti, mrabarnett, Arfrever, tchrist
2011-08-26 21:04:04gvanrossumsetmessageid: <1314392644.0.0.971823116704.issue12728@psf.upfronthosting.co.za>
2011-08-26 21:04:03gvanrossumlinkissue12728 messages
2011-08-26 21:04:03gvanrossumcreate