Message 356018 - 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.

Author	Damien LEFEVRE
Recipients	123 wlpha, Damien LEFEVRE, ronaldoussoren
Date	2019-11-05.10:47:24
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1572950845.0.0.1997358447.issue38680@roundup.psfhosted.org>
In-reply-to

Content
@ronaldoussoren The issue here is that the behavior between Python 3.6 and 3.7 has changed. Our code runs perfectly fine with 3.6. We release the lock each time our functions get out of scope and so we know for sure there is no lock left behind. Starting with 3.7 GIL is acquired when we start the application, but not by us, maybe internally?, and never gets released; thus the deadlock.

@ronaldoussoren

The issue here is that the behavior between Python 3.6 and 3.7 has changed.

Our code runs perfectly fine with 3.6. We release the lock each time our functions get out of scope and so we know for sure there is no lock left behind.

Starting with 3.7 GIL is acquired when we start the application, but not by us, maybe internally?, and never gets released; thus the deadlock.

History
Date	User	Action	Args
2019-11-05 10:47:25	Damien LEFEVRE	set	recipients: + Damien LEFEVRE, ronaldoussoren, 123 wlpha
2019-11-05 10:47:24	Damien LEFEVRE	set	messageid: <1572950845.0.0.1997358447.issue38680@roundup.psfhosted.org>
2019-11-05 10:47:24	Damien LEFEVRE	link	issue38680 messages
2019-11-05 10:47:24	Damien LEFEVRE	create