Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.12] gh-104341: Add a Separate "Running" Lock for Each Thread (gh-104754) #104817

Closed

Conversation

miss-islington
Copy link
Contributor

Having a separate lock means Thread.join() doesn't need to wait for the thread to be cleaned up first. It can wait for the thread's Python target to finish running. This gives us some flexibility in how we clean up threads.

(This is a minor cleanup as part of a fix for gh-104341.)
(cherry picked from commit 097b783)

Co-authored-by: Eric Snow ericsnowcurrently@gmail.com

…ngh-104754)

Having a separate lock means Thread.join() doesn't need to wait for the thread to be cleaned up first.  It can wait for the thread's Python target to finish running.  This gives us some flexibility in how we clean up threads.

(This is a minor cleanup as part of a fix for pythongh-104341.)
(cherry picked from commit 097b783)

Co-authored-by: Eric Snow <ericsnowcurrently@gmail.com>
@gpshead
Copy link
Member

gpshead commented May 24, 2023

this broke main.

@miss-islington miss-islington deleted the backport-097b783-3.12 branch May 24, 2023 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants