Repository navigation
Python doesn't exit with proper resultcode on SIGINT in runpy (pymain_run_module) #85768
Description
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 = <Date 2020-09-22.15:53:35.762>
created_at = <Date 2020-08-20.19:58:37.660>
labels = ['interpreter-core', 'type-bug', '3.8', '3.9', '3.10']
title = "Python doesn't exit with proper resultcode on SIGINT in runpy (pymain_run_module)"
updated_at = <Date 2020-10-05.16:10:20.261>
user = 'https://github.com/graingert'bugs.python.org fields:
activity = <Date 2020-10-05.16:10:20.261>
actor = 'lukasz.langa'
assignee = 'none'
closed = True
closed_date = <Date 2020-09-22.15:53:35.762>
closer = 'gvanrossum'
components = ['Interpreter Core']
creation = <Date 2020-08-20.19:58:37.660>
creator = 'graingert'
dependencies = []
files = ['49414', '49415', '49416', '49417']
hgrepos = []
issue_num = 41602
keywords = ['patch']
message_count = 22.0
messages = ['375732', '375733', '375735', '375736', '375775', '375898', '376984', '377000', '377012', '377013', '377014', '377019', '377020', '377021', '377022', '377024', '377027', '377028', '377339', '377447', '377451', '378057']
nosy_count = 6.0
nosy_names = ['gvanrossum', 'gregory.p.smith', 'ncoghlan', 'lukasz.langa', 'eryksun', 'graingert']
pr_nums = ['21956', '22397', '22398']
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41602'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']
Activity
graingert commentedon Aug 20, 2020
when running "python -m ham.py" KeyboardInterrupt should result in -2, but results in 1
see test case
graingert commentedon Aug 20, 2020
see also https://bugs.python.org/issue1054041
graingert commentedon Aug 20, 2020
I think I've eliminated runpy.py, as I still get a
-2when using:or
see attached test_exit_runpy.py
It seems the only difference is if pymain_run_file or pymain_run_module is used.
[-]Python doesn't exit with proper resultcode on SIGINT in runpy[/-][+]Python doesn't exit with proper resultcode on SIGINT in runpy (pymain_run_module)[/+][-]Python doesn't exit with proper resultcode on SIGINT in runpy[/-][+]Python doesn't exit with proper resultcode on SIGINT in runpy (pymain_run_module)[/+]graingert commentedon Aug 20, 2020
I've now eliminated pymain_run_stdin and pymain_run_command, both process a KeyboardInterrupt as -2
see attached test_exit_command_stdin.py
graingert commentedon Aug 21, 2020
adding vstinner, as this seems related to pymain_run_module rather than runpy
11 remaining items
graingert commentedon Sep 16, 2020
I pushed that patch
gvanrossum commentedon Sep 16, 2020
Why did you remove 3.10?
graingert commentedon Sep 16, 2020
nice the tests pass with that fix
gvanrossum commentedon Sep 22, 2020
New changeset a68a2ad by Thomas Grainger in branch 'master':
bpo-41602: raise SIGINT exit code on KeyboardInterrupt from pymain_run_module (bpo-21956)
a68a2ad
ambv commentedon Sep 24, 2020
New changeset ca8d46d by Łukasz Langa in branch '3.9':
[3.9] bpo-41602: raise SIGINT exit code on KeyboardInterrupt from pymain_run_module (GH-21956) (bpo-22397)
ca8d46d
ambv commentedon Sep 24, 2020
New changeset ae46229 by Thomas Grainger in branch '3.8':
[3.8] bpo-41602: raise SIGINT exit code on KeyboardInterrupt from pymain_run_module (GH-21956) (bpo-22398)
ae46229
ambv commentedon Oct 5, 2020
New changeset c26a666 by Łukasz Langa in branch '3.9':
[3.9] bpo-41602: raise SIGINT exit code on KeyboardInterrupt from pymain_run_module (GH-21956) (bpo-22397)
c26a666