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 bkabrda
Recipients bkabrda, ethan.furman, georg.brandl, ncoghlan, sYnfo, serhiy.storchaka, wolma
Date 2015-03-19.12:50:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1426769436.7.0.284440792953.issue23700@psf.upfronthosting.co.za>
In-reply-to
Content
I'm attaching second version of the patch. It now contains link to this bug and a more real test case according to suggestion from the review.

One of the reviews of first patch version mentioned that there should be a better explanation of how this issue can be provoked. I think that the test shows it nice and there's no need to explain it in greater detail. Also, the comment references this bug, where anyone can find the explanation. (Fix for #18879 fixes pretty much the same in a different method and has very similar comment, so I think this should be fine.)
History
Date User Action Args
2015-03-19 12:50:36bkabrdasetrecipients: + bkabrda, georg.brandl, ncoghlan, ethan.furman, serhiy.storchaka, sYnfo, wolma
2015-03-19 12:50:36bkabrdasetmessageid: <1426769436.7.0.284440792953.issue23700@psf.upfronthosting.co.za>
2015-03-19 12:50:36bkabrdalinkissue23700 messages
2015-03-19 12:50:36bkabrdacreate