multiprocessing: shared manager Pool fails with AttributeError
Open
Nobody has claimed this yet.
stdlib
topic-multiprocessing
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 35919 |
|---|---|
| Nosy | @pitrou, @giampaolo, @applio |
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-02-06.17:36:20.688>
labels = ['3.7', '3.8', 'type-bug', 'library', '3.9']
title = 'multiprocessing: shared manager Pool fails with AttributeError'
updated_at = <Date 2020-07-09.20:12:44.279>
user = 'https://github.com/giampaolo'
bugs.python.org fields:
activity = <Date 2020-07-09.20:12:44.279>
actor = 'Felipe A. Hernandez'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-02-06.17:36:20.688>
creator = 'giampaolo.rodola'
dependencies = []
files = []
hgrepos = []
issue_num = 35919
keywords = []
message_count = 2.0
messages = ['334962', '373427']
nosy_count = 4.0
nosy_names = ['pitrou', 'giampaolo.rodola', 'davin', 'Felipe A. Hernandez']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue35919'
versions = ['Python 3.5', 'Python 3.6', 'Python 3.7', 'Python 3.8', 'Python 3.9']
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 payload identifies a failure in multiprocessing's shared manager Pool but names no source file, test, or reproduction. Start by locating the manager Pool implementation and reproducing the AttributeError; done means the failing scenario works and has 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
- 35/100