max_workers argument to concurrent.futures.ProcessPoolExecutor is not flexible enough
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
topic-multiprocessing
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39617 |
|---|---|
| Nosy | @brianquinlan, @pitrou, @sam-s, @aeros |
| Files |
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 2020-02-12.17:21:04.221>
labels = ['3.8', 'type-feature', 'library']
title = 'max_workers argument to concurrent.futures.ProcessPoolExecutor is not flexible enough'
updated_at = <Date 2021-02-05.05:00:08.426>
user = 'https://github.com/sam-s'
bugs.python.org fields:
activity = <Date 2021-02-05.05:00:08.426>
actor = 'calestyo'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-02-12.17:21:04.221>
creator = 'sam-s'
dependencies = []
files = ['48898']
hgrepos = []
issue_num = 39617
keywords = []
message_count = 6.0
messages = ['361905', '361906', '361956', '362065', '362113', '362351']
nosy_count = 5.0
nosy_names = ['bquinlan', 'pitrou', 'sam-s', 'aeros', 'calestyo']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue39617'
versions = ['Python 3.8']
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
Start with the attached run-at-load-avg.py reproducer and inspect concurrent.futures.ProcessPoolExecutor and its max_workers handling in the Python standard library. Clarify the intended flexibility from the linked BPO discussion, then identify the relevant executor tests; done should include tests that demonstrate the requested behavior and pass without regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100