Multiprocessing.pool API Extension - Pass Data to Workers w/o Globals
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 | 34837 |
|---|---|
| Nosy | @terryjreedy, @pitrou, @applio, @seanharr11 |
| 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 2018-09-28.20:04:13.460>
labels = ['3.8', 'type-feature', 'library']
title = 'Multiprocessing.pool API Extension - Pass Data to Workers w/o Globals'
updated_at = <Date 2018-10-05.18:45:39.587>
user = 'https://github.com/seanharr11'
bugs.python.org fields:
activity = <Date 2018-10-05.18:45:39.587>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-09-28.20:04:13.460>
creator = 'seanharr11'
dependencies = []
files = []
hgrepos = []
issue_num = 34837
keywords = ['patch']
message_count = 2.0
messages = ['327168', '327169']
nosy_count = 4.0
nosy_names = ['terry.reedy', 'pitrou', 'davin', 'seanharr11']
pr_nums = ['9627']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue34837'
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 by reviewing the existing PR 9627 and the multiprocessing.pool library code in Lib. The issue does not identify specific files, tests, or the intended API shape; completion would require an agreed extension that passes data to workers without globals and corresponding validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100