multiprocessing.Server swallows original exception traceback
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
topic-multiprocessing
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 34098 |
|---|---|
| Nosy | @pitrou, @gsalgado, @applio |
| PRs |
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 2018-07-11.15:20:31.789>
labels = ['3.8', 'type-feature', 'library']
title = 'multiprocessing.Server swallows original exception traceback'
updated_at = <Date 2019-03-25.22:49:56.880>
user = 'https://github.com/gsalgado'
bugs.python.org fields:
activity = <Date 2019-03-25.22:49:56.880>
actor = 'cheryl.sabella'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-07-11.15:20:31.789>
creator = 'salgado'
dependencies = []
files = []
hgrepos = []
issue_num = 34098
keywords = ['patch']
message_count = 1.0
messages = ['321480']
nosy_count = 3.0
nosy_names = ['pitrou', 'salgado', 'davin']
pr_nums = ['8254']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue34098'
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
Start by reviewing multiprocessing.Server and the linked PR #8254, then reproduce an exception raised through the server to inspect the traceback that is preserved. Done means the original exception traceback is no longer swallowed and the behavior is covered by an appropriate multiprocessing test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100