This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: IDLE: forward apply patch for handling SystemExit
Type: behavior Stage: resolved
Components: IDLE Versions: Python 3.3, Python 3.4
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: roger.serwy Nosy List: python-dev, rhettinger, roger.serwy, terry.reedy
Priority: low Keywords: patch

Created on 2013-06-12 03:20 by roger.serwy, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
catch_exit.patch roger.serwy, 2013-06-12 03:20 review
Messages (3)
msg191007 - (view) Author: Roger Serwy (roger.serwy) * (Python committer) Date: 2013-06-12 03:20
As a formality, I opened this issue to apply 872a3aca2120 to the 3.x branch. This addresses a concern brought up by Terry in msg187323 from issue5492. Here's the relevant part of the message:

"""
Without or with patch, quit() or exit brings up TK box
(?) The program is still running!
    Do you want to kill it?
    [OK]  [Cancel]
Did this always happen?

[Cancel] causes traceback (not good, regression?)
Traceback (most recent call last):
  File "<pyshell#0>", line 1, in <module>
    quit()
  File "D:\Python\dev\cpython\lib\site.py", line 356, in __call__
    raise SystemExit(code)
SystemExit: None
"""
msg191008 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2013-06-12 03:24
New changeset 0e56d4e37777 by Roger Serwy in branch '3.3':
#18196: Avoid displaying spurious SystemExit tracebacks.
http://hg.python.org/cpython/rev/0e56d4e37777

New changeset 479aad3bb122 by Roger Serwy in branch 'default':
#18196: merge with 3.3
http://hg.python.org/cpython/rev/479aad3bb122
msg191009 - (view) Author: Roger Serwy (roger.serwy) * (Python committer) Date: 2013-06-12 03:25
And it's applied.
History
Date User Action Args
2022-04-11 14:57:46adminsetgithub: 62396
2013-06-12 03:25:54roger.serwysetstatus: open -> closed
resolution: fixed
messages: + msg191009

stage: patch review -> resolved
2013-06-12 03:24:48python-devsetnosy: + python-dev
messages: + msg191008
2013-06-12 03:20:33roger.serwycreate