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 eryksun
Recipients Kevin Shweh, SnoopJeDi, bjs, eryksun, pitrou, serhiy.storchaka, tim.peters, vstinner
Date 2022-02-14.00:39:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1644799195.69.0.720809671882.issue46726@roundup.psfhosted.org>
In-reply-to
Content
> Anything at the Python level that cares whether the thread is 
> still alive will call _wait_for_tstate_lock() again

It's nice that _maintain_shutdown_locks() gets called in _stop(), but the more important call site is in _set_tstate_lock().

I typed up the example initially with try/finally. Then I changed it to avoid the extra lock.locked() call when there's no exception, but I forgot to add a `raise` statement:

        try:
            if lock.acquire_and_release(block, timeout):
                self._stop
        except:
            if not lock.locked():
                self._stop()
            raise
History
Date User Action Args
2022-02-14 00:39:55eryksunsetrecipients: + eryksun, tim.peters, pitrou, vstinner, serhiy.storchaka, Kevin Shweh, bjs, SnoopJeDi
2022-02-14 00:39:55eryksunsetmessageid: <1644799195.69.0.720809671882.issue46726@roundup.psfhosted.org>
2022-02-14 00:39:55eryksunlinkissue46726 messages
2022-02-14 00:39:55eryksuncreate