Message 358641 - Python tracker

➜

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.

In-reply-to
Author	krypticus
Recipients	anselm.kruis, koobs, krypticus, pablogsal, vstinner
Date	2019年12月18日.19:43:46
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1576698226.61.0.943374427011.issue37788@roundup.psfhosted.org>

Content
I ran into this bug as well, and opened an issue for it (before I saw this issue): https://bugs.python.org/issue39074 Was there a conclusion on the best way to fix this? It seems like the previous __del__ implementation would correct the resource leakage by removing the _tstate_lock from _shutdown_locks.

Content

I ran into this bug as well, and opened an issue for it (before I saw this issue): https://bugs.python.org/issue39074
Was there a conclusion on the best way to fix this? It seems like the previous __del__ implementation would correct the resource leakage by removing the _tstate_lock from _shutdown_locks.

History
Date	User	Action	Args
2019年12月18日 19:43:46	krypticus	set	recipients: + krypticus, vstinner, koobs, anselm.kruis, pablogsal
2019年12月18日 19:43:46	krypticus	set	messageid: <1576698226.61.0.943374427011.issue37788@roundup.psfhosted.org>
2019年12月18日 19:43:46	krypticus	link	issue37788 messages
2019年12月18日 19:43:46	krypticus	create

homepage