Author nanjekyejoannah
Recipients docs@python, eric.snow, nanjekyejoannah, ncoghlan, vstinner
Date 2019-08-19.15:31:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1566228661.44.0.499997134577.issue37878@roundup.psfhosted.org>
In-reply-to
Content
From what I know the GIL is released by calling PyEval_ReleaseThread() or PyEval_SaveThread(). 

I see we can use PyThreadState_Delete() to clean up-specifically destroy thread state but does not release the GIL and requires a thread state. On the other hand, PyThreadState_DeleteCurrent() allows to both clean up the current thread state - no thread state is required as well release the GIL which is convenient. I would not fight so much to keep it public given we have PyEval_ReleaseThread() or PyEval_SaveThread().
History
Date User Action Args
2019-08-19 15:31:01nanjekyejoannahsetrecipients: + nanjekyejoannah, ncoghlan, vstinner, docs@python, eric.snow
2019-08-19 15:31:01nanjekyejoannahsetmessageid: <1566228661.44.0.499997134577.issue37878@roundup.psfhosted.org>
2019-08-19 15:31:01nanjekyejoannahlinkissue37878 messages
2019-08-19 15:31:01nanjekyejoannahcreate