Message 413107 - 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	bjs
Recipients	Kevin Shweh, bjs
Date	2022-02-12.00:06:37
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
This is a duplicate of https://bugs.python.org/issue45274 but the patch there did not fix it I've just added a PR there (or should it go here?) that (i think) fixes this. The issue is that the lock.locked() call just checks that someone has the lock, not that the previous acquire() is what got the lock. If it's just that the tstate lock is held because the thread is still running, then it's premature to release() the lock.

This is a duplicate of https://bugs.python.org/issue45274
but the patch there did not fix it

I've just added a PR there (or should it go here?) that (i think) fixes this.

The issue is that the lock.locked() call just checks that *someone* has the lock, not that the previous acquire() is what got the lock.
If it's just that the tstate lock is held because the thread is still running,  then it's premature to release() the lock.

History
Date	User	Action	Args
2022-02-12 00:06:37	bjs	set	recipients: + bjs, Kevin Shweh
2022-02-12 00:06:37	bjs	set	messageid: <[email protected]>
2022-02-12 00:06:37	bjs	link	issue46726 messages
2022-02-12 00:06:37	bjs	create