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 Mark Borgerding
Recipients Joel Croteau, Mark Borgerding, eric.snow, giampaolo.rodola, pablogsal, pitrou, tim.peters
Date 2019-10-29.12:29:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572352197.15.0.811124481934.issue36666@roundup.psfhosted.org>
In-reply-to
Content
@pitrou  I don't necessarily agree that "current behavior can't be changed". One major selling point of exceptions is that they cannot be accidentally ignored.  The exception is how the current threading.Thread ignores them.

You are correct that changing Thread.join() so it propagates exceptions by default may break code that relies on the implicit behavior of a thread dying when the target/run method raises.  I'd argue such code deserves to be broken -- "explicit is better than implicit".

I suspect there is more code that will be fixed by such a change than broken.
History
Date User Action Args
2019-10-29 12:29:57Mark Borgerdingsetrecipients: + Mark Borgerding, tim.peters, pitrou, giampaolo.rodola, eric.snow, pablogsal, Joel Croteau
2019-10-29 12:29:57Mark Borgerdingsetmessageid: <1572352197.15.0.811124481934.issue36666@roundup.psfhosted.org>
2019-10-29 12:29:57Mark Borgerdinglinkissue36666 messages
2019-10-29 12:29:56Mark Borgerdingcreate