gh-137017: Fix Thread.is_alive() to only return False after the underlying OS thread exits#137315
Conversation
…OS thread is fully cleaned up
|
@colesbury, gentle reminder on this PR when you have a moment. |
colesbury
left a comment
There was a problem hiding this comment.
Thanks @abdoulrasheed. Looks good with a minor comment below
|
Thanks @abdoulrasheed for the PR, and @colesbury for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
|
Thanks @abdoulrasheed for the PR, and @colesbury for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
…the underlying OS thread exits (pythongh-137315) (cherry picked from commit aa9ceb1) Co-authored-by: Abdul <abdulrasheedibrahim47@gmail.com>
…the underlying OS thread exits (pythongh-137315) (cherry picked from commit aa9ceb1) Co-authored-by: Abdul <abdulrasheedibrahim47@gmail.com>
|
GH-138916 is a backport of this pull request to the 3.14 branch. |
|
GH-138917 is a backport of this pull request to the 3.13 branch. |
|
Ensure
Thread.is_alive()only returns False after the underlying OS thread exits.Thread.is_aliveshould only returnFalseafter a thread exits (once it's started) #137017