➜

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 pitrou
Recipients eric.snow, nanjekyejoannah, ncoghlan, pablogsal, pconnell, pitrou, tim.peters, vstinner
Date 2019-12-21.20:15:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content 
> 1. Python daemon threads

I think the answer is to document a bit more clearly that they can pose all kinds of problems.  Perhaps we could even display a visible warning when people create daemon threads.

> 2. Python threads created in atexit handlers

We could run the "join non-daemon threads" routine a *second time* after atexit handlers have been called.  It probably can't hurt (unless people do silly things?).

> 3. non-Python threads accessing the C-API

This one I don't know how to handle. By construction, a non-Python thread can do anything it wants, and we cannot add guards against this at the beginning of each C API function. I think that when someone calls the C API, we're clearly in the realm of "consenting adults".
History
Date User Action Args
2019-12-21 20:15:13pitrousetrecipients: + pitrou, tim.peters, ncoghlan, vstinner, eric.snow, pconnell, pablogsal, nanjekyejoannah
2019-12-21 20:15:13pitrousetmessageid: <[email protected]>
2019-12-21 20:15:13pitroulinkissue36476 messages
2019-12-21 20:15:13pitroucreate