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 gvanrossum
Recipients asvetlov, gvanrossum, iritkatriel, yselivanov
Date 2021-11-29.18:21:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
There's a similar issue with concurrent.futures.Future, and really, anything that stores exceptions and later raises them can get in trouble if there's a way to get the exception raised multiple times. This is rarely noticed because usually the exception isn't raised more than once. 

We need separate bpo issues for the other cases.

The fix is easy enough (separately store a traceback and raise using e.with_traceback(tb)) so I'm marking this as an easy issue.
Date User Action Args
2021-11-29 18:21:26gvanrossumsetrecipients: + gvanrossum, asvetlov, yselivanov, iritkatriel
2021-11-29 18:21:26gvanrossumsetmessageid: <>
2021-11-29 18:21:26gvanrossumlinkissue45924 messages
2021-11-29 18:21:26gvanrossumcreate