Multiprocessing.Manager: fix behavior and doc inconsistencies
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- distributed-systems, documentation
Research direction
Start by reading the linked mp_test.py test file and running it with psutil installed, then inspect the multiprocessing.Manager implementation and documentation it exercises. Done means the demonstrated behavior and the corresponding documentation are consistent, with the relevant tests passing.
Written by the indexing model from the issue text.
Description
| BPO | 23698 |
|---|---|
| Nosy | @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 2015-03-18.06:33:05.034>
labels = ['type-bug', 'library', 'docs']
title = 'Multiprocessing.Manager: fix behavior and doc inconsistencies'
updated_at = <Date 2015-05-14.09:47:40.734>
user = 'https://bugs.python.org/pythonhacker'
bugs.python.org fields:
activity = <Date 2015-05-14.09:47:40.734>
actor = 'pythonhacker'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Library (Lib)']
creation = <Date 2015-03-18.06:33:05.034>
creator = 'pythonhacker'
dependencies = []
files = ['38537']
hgrepos = []
issue_num = 23698
keywords = []
message_count = 5.0
messages = ['238379', '238430', '238524', '238525', '243165']
nosy_count = 4.0
nosy_names = ['pythonhacker', 'docs@python', 'sbt', 'davin']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue23698'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100