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 Joel Croteau
Recipients Joel Croteau, giampaolo.rodola, pablogsal, pitrou, tim.peters
Date 2019-04-19.20:41:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1555706498.54.0.341854467544.issue36666@roundup.psfhosted.org>
In-reply-to
Content
I agree that we should not change the default behavior of Thread.join(), as that would break existing code, but there are plenty of other ways to do this. I see a couple of possibilities:

1. Add an option to the Thread constructor, something like raise_exc, that defaults to False, but when set to True, causes join() to raise any exceptions.

2. (Better, IMO) Add this option to the join() method instead.

3. Create a new method, join_with_exc(), that acts like join() but raises exceptions from the target.

4. (Should probably do this anyway, regardless of what else we do) Add a new method, check_exc(), that checks if any unhandled exceptions have occurred in the thread and returns and/or raises any that have.
History
Date User Action Args
2019-04-19 20:41:38Joel Croteausetrecipients: + Joel Croteau, tim.peters, pitrou, giampaolo.rodola, pablogsal
2019-04-19 20:41:38Joel Croteausetmessageid: <1555706498.54.0.341854467544.issue36666@roundup.psfhosted.org>
2019-04-19 20:41:38Joel Croteaulinkissue36666 messages
2019-04-19 20:41:38Joel Croteaucreate