Expose `worker_target` and `workitem_cls` as arugments to customize `ThreadPoolExecutor` behaviour
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 31357 |
|---|---|
| Nosy | @justdoit0823 |
| PRs |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2017-09-06.00:14:20.180>
labels = ['3.7', 'type-feature', 'library']
title = 'Expose `worker_target` and `workitem_cls` as arugments to customize `ThreadPoolExecutor` behaviour'
updated_at = <Date 2022-01-24.22:42:12.007>
user = 'https://github.com/justdoit0823'
bugs.python.org fields:
activity = <Date 2022-01-24.22:42:12.007>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-09-06.00:14:20.180>
creator = 'justdoit0823'
dependencies = []
files = []
hgrepos = []
issue_num = 31357
keywords = []
message_count = 1.0
messages = ['301414']
nosy_count = 1.0
nosy_names = ['justdoit0823']
pr_nums = ['3268']
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue31357'
versions = ['Python 3.7']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue identifies ThreadPoolExecutor and existing PR #3268 as starting points. Review that PR and the current executor implementation to determine the intended public arguments and whether the request remains applicable. Done means the requested customization is exposed and covered by the project's relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100