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 MrJean1, alanmcintyre, donmez, facundobatista, giampaolo.rodola, josiahcarlson, mark.dickinson, r.david.murray
Date 2009-05-07.17:27:42
SpamBayes Score 3.4717154e-09
Marked as misclassified No
Message-id <1241717265.37.0.95832921282.issue5798@psf.upfronthosting.co.za>
In-reply-to
Content
See also issue 1161031, especially Giampaolo's suggestion near the end.
 Seems like it might be relevant.  I was the one who merged Josiah's
trunk fix into othe other branches, to get things back into sync, but I
don't claim to understand the code at any deep level.  From the review I
did at my level of knowledge it seems like the change to the behavior of
when handle_expt_event is called is correct, but I was a little worried
about backward compatibility.  I now wonder if that fix should be backed
out of 2.6 and 3.0, and advertised in What's New for 2.7 and 3.1.
History
Date User Action Args
2009-05-07 17:27:45r.david.murraysetrecipients: + r.david.murray, facundobatista, josiahcarlson, mark.dickinson, alanmcintyre, giampaolo.rodola, donmez, MrJean1
2009-05-07 17:27:45r.david.murraysetmessageid: <1241717265.37.0.95832921282.issue5798@psf.upfronthosting.co.za>
2009-05-07 17:27:43r.david.murraylinkissue5798 messages
2009-05-07 17:27:42r.david.murraycreate