multiprocessing.Manager objects lose connection info
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 | 41660 |
|---|---|
| Nosy | @tim-one |
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-08-28.23:48:19.765>
labels = ['3.8', 'type-bug', 'library']
title = 'multiprocessing.Manager objects lose connection info'
updated_at = <Date 2020-08-29.21:31:57.157>
user = 'https://github.com/tim-one'
bugs.python.org fields:
activity = <Date 2020-08-29.21:31:57.157>
actor = 'tim.peters'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-08-28.23:48:19.765>
creator = 'tim.peters'
dependencies = []
files = []
hgrepos = []
issue_num = 41660
keywords = []
message_count = 4.0
messages = ['376051', '376052', '376078', '376082']
nosy_count = 1.0
nosy_names = ['tim.peters']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41660'
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
No source file, test, or entry point is named. Start with BPO 41660 and the four migrated comments to identify the missing connection information and a reproducible Manager case, then locate the relevant multiprocessing code. Done means the behavior is covered by a regression test and Manager objects retain the expected connection information.
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