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 r.david.murray
Recipients alex, benjamin.peterson, gregory.p.smith, hynek, nikratio, pitrou, python-dev, r.david.murray, serhiy.storchaka, stutzbach, vajrasky
Date 2013-07-10.21:13:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1373490837.91.0.709112027743.issue18116@psf.upfronthosting.co.za>
In-reply-to
Content
I played around with this for a bit, but I couldn't come up with any test improvements, or any way to test the bug that is being fixed.  So I just committed it as is.  Thanks, Serhiy.  And thanks Vajrasky for giving it a try and figuring out some of the stuff that *doesn't* work as a fix :)

I decided to only commit this to 3.4.  I don't think the risk of an unexpected behavior change in a maintenance release is worth the relatively small benefit that this fix provides.
History
Date User Action Args
2013-07-10 21:13:57r.david.murraysetrecipients: + r.david.murray, gregory.p.smith, pitrou, benjamin.peterson, stutzbach, alex, nikratio, python-dev, hynek, serhiy.storchaka, vajrasky
2013-07-10 21:13:57r.david.murraysetmessageid: <1373490837.91.0.709112027743.issue18116@psf.upfronthosting.co.za>
2013-07-10 21:13:57r.david.murraylinkissue18116 messages
2013-07-10 21:13:57r.david.murraycreate