[issue26949] IDLE restarts when one debugs code raising SystemExit

2019-09-20 Thread Terry J. Reedy
Terry J. Reedy added the comment: >>> raise SystemExit does not normally cause a restart. -- nosy: -kbk, roger.serwy versions: +Python 3.9 -Python 2.7, Python 3.5, Python 3.6 ___ Python tracker

[issue26949] IDLE restarts when one debugs code raising SystemExit

2017-05-30 Thread Terry J. Reedy
Terry J. Reedy added the comment: Louie> If you run your example in Python with -i, you will see the same behavior, except for the traceback, as with IDLE. F:\dev\cpython>python -i -c "x=10; print(x); raise SystemExit" Running Debug|Win32 interpreter... 10 Traceback (most recent call last): F

[issue26949] IDLE restarts when one debugs code raising SystemExit

2017-05-21 Thread Louie Lu
Louie Lu added the comment: PR 1711 fix KeyboardInterrupt with adding rpc.repsonse_queue.put, but it will not print out the exception traceback. And for SystemExit, wait for discussion result. -- ___ Python tracker

[issue26949] IDLE restarts when one debugs code raising SystemExit

2017-05-21 Thread Louie Lu
Changes by Louie Lu : -- pull_requests: +1802 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue26949] IDLE restarts when one debugs code raising SystemExit

2017-05-21 Thread Louie Lu
Louie Lu added the comment: The problem is cause by run.py:main function, when it catch KeyboardInterrupt or SystemExit, it won't put a blank msg back to response_queue, that cause the loop in run.py:main triggering except queue.Empty to continue the loop. So, I think the KeyboardInterrupt h

[issue26949] IDLE restarts when one debugs code raising SystemExit

2016-05-07 Thread Terry J. Reedy
Terry J. Reedy added the comment: #14111 is about handling ^C while debugging. So for now I will assume that handling 'raise KeyboardInterrupt' is part of that issue. -- ___ Python tracker ___

[issue26949] IDLE restarts when one debugs code raising SystemExit

2016-05-07 Thread ppperry
ppperry added the comment: This issue has worse consequences than I previously thought. It also affects `KeyboardInterrupt` with worse consequences. If you run a program raising `KeyboardInterrupt` in the debugger, the shell will hang. Restarting the shell fixes this problem. --

[issue26949] IDLE restarts when one debugs code raising SystemExit

2016-05-04 Thread Terry J. Reedy
Terry J. Reedy added the comment: Thanks, that may make debugging this (and creating a test) easier. I have only seriously used debugger with files, and often with breakpoints in the file. -- versions: +Python 3.5, Python 3.6 -Python 3.4 ___ Python

[issue26949] IDLE restarts when one debugs code raising SystemExit

2016-05-04 Thread ppperry
ppperry added the comment: Terry, Your `how to reproduce` is more complicated than necessary. This bug can be reproduced by just turning on the debugger in a python shell and typing `raise SystemExit` then pressing step in the debugger. -- versions: +Python 2.7 ___

[issue26949] IDLE restarts when one debugs code raising SystemExit

2016-05-04 Thread Terry J. Reedy
New submission from Terry J. Reedy: To be more specific: if one runs a file, the shell is restarted (with the file name). In the file, raise SystemExit is normally the same as running off the end of the file, and a prompt is printed. If one runs a file with debugger on, [DEBUG ON] is printed

[issue26949] IDLE restarts when one debugs code raising SystemExit

2016-05-04 Thread SilentGhost
Changes by SilentGhost : -- nosy: +kbk, roger.serwy, terry.reedy stage: -> test needed ___ Python tracker ___ ___ Python-bugs-list ma

[issue26949] IDLE restarts when one debugs code raising SystemExit

2016-05-04 Thread ppperry
Changes by ppperry : -- components: IDLE nosy: ppperry priority: normal severity: normal status: open title: IDLE restarts when one debugs code raising SystemExit type: behavior versions: Python 3.4 ___ Python tracker