Possible glitch in the interaction of a thread and a multiprocessing manager
Open
Nobody has claimed this yet.
interpreter-core
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 29158 |
|---|---|
| Nosy | @bitdancer, @ethanfurman, @applio |
| 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 2017-01-04.19:19:03.378>
labels = ['interpreter-core', 'type-bug']
title = 'Possible glitch in the interaction of a thread and a multiprocessing manager'
updated_at = <Date 2021-06-19.01:01:58.106>
user = 'https://bugs.python.org/luke16'
bugs.python.org fields:
activity = <Date 2021-06-19.01:01:58.106>
actor = 'ethan.furman'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2017-01-04.19:19:03.378>
creator = 'luke_16'
dependencies = []
files = ['46145', '46159']
hgrepos = []
issue_num = 29158
keywords = []
message_count = 5.0
messages = ['284661', '284662', '284674', '284740', '284835']
nosy_count = 4.0
nosy_names = ['r.david.murray', 'ethan.furman', 'davin', 'luke_16']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue29158'
versions = ['Python 2.7', 'Python 3.6']
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 examining and running the attached case.zip and case2.zip reproductions, which contain the three Python modules demonstrating the thread and multiprocessing manager interaction. Determine the expected behavior and isolate the interpreter-core failure; done requires a confirmed fix and a regression test for the reproduced scenario.
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
- 25/100