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 serhiy.storchaka
Recipients georg.brandl, gvanrossum, serhiy.storchaka, vstinner
Date 2014-12-15.23:38:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1418686717.56.0.403405831895.issue23055@psf.upfronthosting.co.za>
In-reply-to
Content
I have added a couple of comments. Here is a patch which fixes found bugs.

3.4+ is not affected by this bug. 3.2 looks same as 2.7 and is affected, 3.3 uses different code but at first glance looks affected too. Is it worth to fix this bug in 3.2 and 3.3?
History
Date User Action Args
2014-12-15 23:38:37serhiy.storchakasetrecipients: + serhiy.storchaka, gvanrossum, georg.brandl, vstinner
2014-12-15 23:38:37serhiy.storchakasetmessageid: <1418686717.56.0.403405831895.issue23055@psf.upfronthosting.co.za>
2014-12-15 23:38:37serhiy.storchakalinkissue23055 messages
2014-12-15 23:38:37serhiy.storchakacreate