multiprocessing Pool should allow custom task queue
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 32/100
Research direction
Start by reading the multiprocessing Pool implementation around _setup_queues and the historical multiproc.patch, which sets up _taskqueue there. Trace how Pool currently creates and uses its task queue before deciding what customization the public API should support. Done means Pool users can provide a custom task queue, with behavior covered by appropriate multiprocessing tests.
Written by the indexing model from the issue text.
Description
| BPO | 6407 |
|---|---|
| Nosy | @pitrou, @akheron, @iritkatriel |
| 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 2009-07-03.13:23:17.286>
labels = ['type-feature', 'library']
title = 'multiprocessing Pool should allow custom task queue'
updated_at = <Date 2021-06-29.19:09:17.430>
user = 'https://bugs.python.org/masher'
bugs.python.org fields:
activity = <Date 2021-06-29.19:09:17.430>
actor = 'iritkatriel'
assignee = 'jnoller'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2009-07-03.13:23:17.286>
creator = 'masher'
dependencies = []
files = ['14442']
hgrepos = []
issue_num = 6407
keywords = ['patch']
message_count = 12.0
messages = ['90052', '90056', '90067', '90070', '115259', '115260', '119499', '119511', '148170', '148244', '148246', '396753']
nosy_count = 7.0
nosy_names = ['pitrou', 'jnoller', 'asksol', 'masher', 'petri.lehtinen', 'swindmill', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue6407'
versions = ['Python 3.3']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100