multiprocessing Server's shutdown method useless send message to manager
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 | 32014 |
|---|---|
| Nosy | @pitrou, @applio, @subler |
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-11-13.06:00:30.342>
labels = ['type-bug', 'library']
title = "multiprocessing Server's shutdown method useless send message to manager"
updated_at = <Date 2017-11-13.06:00:30.342>
user = 'https://github.com/subler'
bugs.python.org fields:
activity = <Date 2017-11-13.06:00:30.342>
actor = 'stevezh'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-11-13.06:00:30.342>
creator = 'stevezh'
dependencies = []
files = []
hgrepos = []
issue_num = 32014
keywords = []
message_count = 1.0
messages = ['306142']
nosy_count = 5.0
nosy_names = ['pitrou', 'jnoller', 'sbt', 'davin', 'stevezh']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue32014'
versions = ['Python 3.5', '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 at the multiprocessing Server.shutdown entry point and trace how it sends a message to the manager; the issue provides no file or test to narrow the search. Reproduce the shutdown behavior and establish a regression test for the corrected manager communication, confirming the expected behavior with maintainers first.
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
- 30/100