Python doesn't exit with proper resultcode on SIGINT in multiprocessing.Process
Open
Nobody has claimed this yet.
3.10
3.11
3.8 (EOL)
3.9 (EOL)
interpreter-core
topic-multiprocessing
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 45023 |
|---|---|
| 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 2021-08-26.22:56:33.544>
labels = ['interpreter-core', '3.8', '3.9', '3.10', '3.11']
title = "Python doesn't exit with proper resultcode on SIGINT in multiprocessing.Process"
updated_at = <Date 2021-08-26.22:56:33.544>
user = 'https://bugs.python.org/ambwrig'
bugs.python.org fields:
activity = <Date 2021-08-26.22:56:33.544>
actor = 'ambwrig'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2021-08-26.22:56:33.544>
creator = 'ambwrig'
dependencies = []
files = ['50237']
hgrepos = []
issue_num = 45023
keywords = []
message_count = 1.0
messages = ['400384']
nosy_count = 1.0
nosy_names = ['ambwrig']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue45023'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10', 'Python 3.11']
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 with the reproducible example in test.py and run it to observe the exit result when multiprocessing.Process receives SIGINT. Trace the relevant interpreter-core and multiprocessing behavior, then verify that the process exits with the expected result code and that the regression is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100