-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
bpo-29212: Fix the ugly repr() ThreadPoolExecutor thread name. #2315
Merged
gpshead
merged 2 commits into
python:master
from
gpshead:issue29212-threadpoolexecutor-name
Jun 22, 2017
Merged
bpo-29212: Fix the ugly repr() ThreadPoolExecutor thread name. #2315
gpshead
merged 2 commits into
python:master
from
gpshead:issue29212-threadpoolexecutor-name
Jun 22, 2017
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
methane
approved these changes
Jun 21, 2017
The commit message has a typo at the end: |
Fixes the newly introduced ugly default thread name for concurrent.futures thread.ThreadPoolExecutor threads. They'll now resemble the old <=3.5 threading default Thread-x names by being named ThreadPoolExecutor-y_n.
c06b002
to
415f28b
Compare
sseg
added a commit
to sseg/pythonfutures
that referenced
this pull request
Aug 8, 2017
sseg
added a commit
to sseg/pythonfutures
that referenced
this pull request
Aug 8, 2017
sseg
added a commit
to sseg/pythonfutures
that referenced
this pull request
Aug 8, 2017
agronholm
pushed a commit
to agronholm/pythonfutures
that referenced
this pull request
Aug 8, 2017
Changes from python/cpython#2315 Fixes #63.
gpshead
added a commit
to gpshead/cpython
that referenced
this pull request
Sep 3, 2017
…ythonGH-2315) bpo-29212: Fix the ugly ThreadPoolExecutor thread name. Fixes the newly introduced ugly default thread name for concurrent.futures thread.ThreadPoolExecutor threads. They'll now resemble the old <=3.5 threading default Thread-x names by being named ThreadPoolExecutor-y_n.. (cherry picked from commit a3d91b4)
gpshead
added a commit
that referenced
this pull request
Sep 3, 2017
…H-2315) (#3276) bpo-29212: Fix the ugly ThreadPoolExecutor thread name. Fixes the newly introduced ugly default thread name for concurrent.futures thread.ThreadPoolExecutor threads. They'll now resemble the old <=3.5 threading default Thread-x names by being named ThreadPoolExecutor-y_n.. (cherry picked from commit a3d91b4)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes the newly introduced ugly default thread name for concurrent.futures
thread.ThreadPoolExecutor threads. They'll now resemble the old <=3.5
threading default Thread-x names by being named ThreadPoolExecutor-y_n.