shared memory problems with multiprocessing.Pool
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 | 40828 |
|---|---|
| Nosy | @pitrou, @applio, @vinay0410, @trapezoid677 |
| 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-05-30.17:57:21.554>
labels = ['3.8', 'type-bug', 'library']
title = 'shared memory problems with multiprocessing.Pool'
updated_at = <Date 2020-07-19.07:15:02.005>
user = 'https://github.com/trapezoid677'
bugs.python.org fields:
activity = <Date 2020-07-19.07:15:02.005>
actor = 'vinay0410'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-05-30.17:57:21.554>
creator = 'trapezoid677'
dependencies = []
files = ['49203']
hgrepos = []
issue_num = 40828
keywords = []
message_count = 2.0
messages = ['370396', '373938']
nosy_count = 4.0
nosy_names = ['pitrou', 'davin', 'vinay0410', 'trapezoid677']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue40828'
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 reading the linked shared_memory.py file and tracing how it interacts with multiprocessing.Pool. Reproduce the reported shared-memory problem, then confirm that the affected Pool workflow behaves correctly without introducing regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100