➜

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 BTaskaya, arekm, gaborjbernat, miss-islington, pablogsal, vstinner
Date 2020-03-20.17:47:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1584726430.74.0.108460379705.issue39360@roundup.psfhosted.org>
In-reply-to
Content 
commit 4d96b4635aeff1b8ad41d41422ce808ce0b971c8
"bpo-39511: PyThreadState_Clear() calls on_delete (GH-18296)"

"(...) The release_sentinel() function is now called when the C API is still
fully working."

This change is "safer" than the other one, but there is still a risk of introducing a regression.

The problem is that this commit is part of a larger effort to make the Python finalization more reliable. The commit makes sense in the serie of commits pushed into the master branch, but I'm not sure that it makes sense if it's taken alone.

I don't have the bandwidth right now to investigate this issue, to identify the root issue, and suggest which commits should be backported or not.
History
Date User Action Args
2020-03-20 17:47:10vstinnersetrecipients: + vstinner, arekm, pablogsal, miss-islington, gaborjbernat, BTaskaya
2020-03-20 17:47:10vstinnersetmessageid: <1584726430.74.0.108460379705.issue39360@roundup.psfhosted.org>
2020-03-20 17:47:10vstinnerlinkissue39360 messages
2020-03-20 17:47:10vstinnercreate