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 vstinner
Recipients eric.snow, nanjekyejoannah, ncoghlan, pablogsal, vstinner
Date 2020-03-11.23:14:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1583968450.71.0.0803305468222.issue39877@roundup.psfhosted.org>
In-reply-to
Content
The initial issue is now fixed. I close the issue.

take_gil() only checks if the thread must exit once the GIL is acquired. Maybe it would be able to exit earlier, but I took the safe approach. If we must exit, drop the GIL and then exit. That's basically Python 3.8 behavior.

If someone wants to optimize/enhance take_gil() for daemon thread, I suggest to open a new issue.

Note: Supporting daemon threads require tricky code in take_gil(). I would prefer to deprecate daemon threads and prepare their removal.
History
Date User Action Args
2020-03-11 23:14:10vstinnersetrecipients: + vstinner, ncoghlan, eric.snow, pablogsal, nanjekyejoannah
2020-03-11 23:14:10vstinnersetmessageid: <1583968450.71.0.0803305468222.issue39877@roundup.psfhosted.org>
2020-03-11 23:14:10vstinnerlinkissue39877 messages
2020-03-11 23:14:10vstinnercreate