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 r.david.murray, the.mulhern, vinay.sajip, yselivanov
Date 2014-03-14.12:46:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1394801208.9.0.560007307081.issue20918@psf.upfronthosting.co.za>
In-reply-to
Content
Yes on 3.3 fixes, but you are right that it doesn't need fixed there.  This appears to be a 3.4 regression.  I used exactly the test you suggest to reproduce it on 3.4...there there is a chained traceback and Done does not get printed.  So, the original report is indeed invalid, but we've uncovered a regression.  Fortunately it is a low impact regression.

I'm guessing this arises from the improvements you made to the "fallback" logging of these errors.
History
Date User Action Args
2014-03-14 12:46:48r.david.murraysetrecipients: + r.david.murray, vinay.sajip, yselivanov, the.mulhern
2014-03-14 12:46:48r.david.murraysetmessageid: <1394801208.9.0.560007307081.issue20918@psf.upfronthosting.co.za>
2014-03-14 12:46:48r.david.murraylinkissue20918 messages
2014-03-14 12:46:48r.david.murraycreate