-
Notifications
You must be signed in to change notification settings - Fork 47
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
Backport: Issue #27664: Allow specifying prefix for thread name in concurrent.futures.ThreadPoolExecutor #63
Comments
sseg
added a commit
to sseg/pythonfutures
that referenced
this issue
Jul 26, 2017
Add optional `thread_name_prefix` argument to constructor of ThreadPoolExecutor. Resolves agronholm#63
agronholm
pushed a commit
that referenced
this issue
Aug 8, 2017
Changes from python/cpython#2315 Fixes #63.
@agronholm Any idea when this will make it in a release? |
I can make a new release any time. Nothing else is in the pipeline for this project right now so I don't mind. |
That would be great! |
Right, I had forgotten about #66 |
I've released v3.2.0 now. |
Thanks! |
dhermes
added a commit
to dhermes/google-cloud-python
that referenced
this issue
Dec 4, 2017
dhermes
added a commit
to googleapis/google-cloud-python
that referenced
this issue
Dec 4, 2017
busunkim96
pushed a commit
to googleapis/python-api-core
that referenced
this issue
Jan 7, 2020
plamut
pushed a commit
to googleapis/python-pubsub
that referenced
this issue
Jan 31, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please consider including the changes for thread_name_prefix:
http://bugs.python.org/issue27664, commit: python/cpython@50abe87
The text was updated successfully, but these errors were encountered: