Multiprocessing resolving object as None
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 | 39414 |
|---|---|
| Nosy | @pitrou, @applio, @corona10, @RDIL |
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-01-21.17:07:47.906>
labels = ['3.8', 'type-bug', 'library']
title = 'Multiprocessing resolving object as None'
updated_at = <Date 2020-04-06.02:45:54.867>
user = 'https://github.com/RDIL'
bugs.python.org fields:
activity = <Date 2020-04-06.02:45:54.867>
actor = 'Talley Lambert'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-01-21.17:07:47.906>
creator = 'rdil'
dependencies = []
files = []
hgrepos = []
issue_num = 39414
keywords = []
message_count = 4.0
messages = ['360407', '360409', '360411', '365837']
nosy_count = 5.0
nosy_names = ['pitrou', 'davin', 'corona10', 'rdil', 'Talley Lambert']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue39414'
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
The issue body provides no source file, test, reproduction, or entry point beyond the multiprocessing component and the original BPO 39414 link. Start by reading the linked report and locating the relevant multiprocessing behavior. Done should mean the reported object-resolution problem is reproduced, its expected behavior is defined, and a regression test demonstrates the fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100