Message 290751 - Python tracker

➜

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.

Author	terry.reedy
Recipients	Mark, eryksun, njs, terry.reedy
Date	2017-03-28.18:24:40
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1490725480.17.0.0354723643684.issue29926@psf.upfronthosting.co.za>
In-reply-to

Content
Even is IDLE is started from a console, the user execution process is not attached to one. What I want, from an IDLE perspective, is for ^C in IDLE's shell to work as well as it does in a terminal. That means either fixing _thread.interrupt_main to always do what it usually does (from a user perspective), or to be given something else to use in .interrupt_the_server() that does so. The current workaround for stopping runaway code in interactive mode, restarting the shell with cntl-F6 or the menu entry Shell => Restart Shell, is a) obscure and not known to most beginners, and b) does too much in that it throws away the workspace. It is much like closing a terminal Window with [X], and restarting the terminal and python, instead of using ^C. Viktor, I am nosying you because of your posts to #21895. Do you have any comments on this issue?

Even is IDLE is started from a console, the user execution process is not attached to one.

What I want, from an IDLE perspective, is for ^C in IDLE's shell to work as well as it does in a terminal.  That means either fixing _thread.interrupt_main to always do what it usually does (from a user perspective), or to be given something else to use in .interrupt_the_server() that does so.

The current workaround for stopping runaway code in interactive mode, restarting the shell with cntl-F6 or the menu entry Shell => Restart Shell, is a) obscure and not known to most beginners, and b) does too much in that it throws away the workspace.  It is much like closing a terminal Window with [X], and restarting the terminal and python, instead of using ^C.

Viktor, I am nosying you because of your posts to #21895.  Do you have any comments on this issue?

History
Date	User	Action	Args
2017-03-28 18:24:40	terry.reedy	set	recipients: + terry.reedy, njs, Mark, eryksun
2017-03-28 18:24:40	terry.reedy	set	messageid: <1490725480.17.0.0354723643684.issue29926@psf.upfronthosting.co.za>
2017-03-28 18:24:40	terry.reedy	link	issue29926 messages
2017-03-28 18:24:40	terry.reedy	create