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

bpo-29212: Fix the ugly repr() ThreadPoolExecutor thread name. #2315

Merged
merged 2 commits into from
Jun 22, 2017

Conversation

gpshead
Copy link
Member

@gpshead gpshead commented Jun 21, 2017

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.

@mlouielu
Copy link
Contributor

The commit message has a typo at the end: ThreadPoolExecutur-y_z -> ThreadPoolExecutor-y_z.

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.
@gpshead gpshead force-pushed the issue29212-threadpoolexecutor-name branch from c06b002 to 415f28b Compare June 22, 2017 06:20
@gpshead gpshead merged commit a3d91b4 into python:master Jun 22, 2017
@gpshead gpshead deleted the issue29212-threadpoolexecutor-name branch June 22, 2017 06:41
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
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants