Issue with multiprocessing.Pool & multiprocessing.Queue
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 38833 |
|---|---|
| Nosy | @bigbizze |
| 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 2019-11-17.17:42:34.527>
labels = ['3.8', 'type-bug', 'library']
title = 'Issue with multiprocessing.Pool & multiprocessing.Queue'
updated_at = <Date 2019-11-17.17:42:34.527>
user = 'https://github.com/bigbizze'
bugs.python.org fields:
activity = <Date 2019-11-17.17:42:34.527>
actor = 'bigbizze'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-11-17.17:42:34.527>
creator = 'bigbizze'
dependencies = []
files = ['48719']
hgrepos = []
issue_num = 38833
keywords = []
message_count = 1.0
messages = ['356822']
nosy_count = 1.0
nosy_names = ['bigbizze']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue38833'
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 python_mp_pool_queue_issue.py reproducer and inspect the interaction between multiprocessing.Pool and multiprocessing.Queue. Reproduce the reported behavior, determine the expected result from the issue context, and use that to define the required fix and regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100