-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
gh-136470: Correct InterpreterPoolExecutor's default thread name #136472
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
gh-136470: Correct InterpreterPoolExecutor's default thread name #136472
Conversation
Misc/NEWS.d/next/Library/2025-07-10-00-47-37.gh-issue-136470.KlUEUG.rst
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly LGTM
!buildbot ^((?!refleak).)* PR$ |
🤖 New build scheduled with the buildbot fleet by @ZeroIntensity for commit 43da83f 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F136472%2Fmerge The command will test the builders whose names match following regular expression: The builders matched are:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The failures look unrelated, I think I triggered a few outdated buildbots.
Thanks @aisk for the PR, and @ZeroIntensity for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
pythonGH-136472) The OS thread name is now correctly prefixed with `InterpreterPoolExecutor` instead of `ThreadPoolExecutor`. (cherry picked from commit 246be21) Co-authored-by: AN Long <aisk@users.noreply.github.com>
GH-136889 is a backport of this pull request to the 3.14 branch. |
…me (GH-136472) (GH-136889) gh-136470: Correct InterpreterPoolExecutor's default thread name (GH-136472) The OS thread name is now correctly prefixed with `InterpreterPoolExecutor` instead of `ThreadPoolExecutor`. (cherry picked from commit 246be21) Co-authored-by: AN Long <aisk@users.noreply.github.com>
After this change, the custom thread name will became:
InterpreterPoolExecutor
's default thread name prefix is invalid #136470