Interrupting subprocess.popen in recursive calls by KeyboardInterrupt causes Fatal Python error.
Open
Nobody has claimed this yet.
3.10
3.11
3.9 (EOL)
interpreter-core
type-crash
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 46115 |
|---|
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-12-17.11:14:30.500>
labels = ['interpreter-core', '3.10', '3.9', 'type-crash', '3.11']
title = 'Interrupting subprocess.popen in recursive calls by KeyboardInterrupt causes Fatal Python error.'
updated_at = <Date 2022-01-17.22:34:29.742>
user = 'https://bugs.python.org/xxm'
bugs.python.org fields:
activity = <Date 2022-01-17.22:34:29.742>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2021-12-17.11:14:30.500>
creator = 'xxm'
dependencies = []
files = []
hgrepos = []
issue_num = 46115
keywords = []
message_count = 1.0
messages = ['408772']
nosy_count = 1.0
nosy_names = ['xxm']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue46115'
versions = ['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
The issue names recursive subprocess.popen calls and KeyboardInterrupt as the failing entry points, but provides no source file, reproducer, or test. Start by reproducing the fatal error around that interaction, then trace the interpreter and subprocess handling involved. Done means the recursive interruption no longer causes a Fatal Python error and a regression test covers it.
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
- 25/100