-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPython Console: Cannot interrupt started processes #1078
Comments
From ccordoba12 on 2012-06-15T20:10:14Z I have code in my personal repo that solves this issue (and also kernel restarts). It's still not ready to push but I think it's not necessary for anyone else to invest time on it. |
From ccordoba12 on 2012-06-18T11:48:24Z This issue was updated by revision e62ec90fb10d .
|
From ccordoba12 on 2012-06-18T11:56:44Z Jed, could test this change works as expected and close the issue? It would be a matter of hitting Ctrl+C to stop a computation or to use the option I introduced in the new menu. |
From jed.lud...@gmail.com on 2012-06-19T06:41:08Z Seems to be working correctly on Windows. Status: Verified |
From ccordoba12 on 2012-07-05T20:14:35Z Blocking: spyderlib:1053 |
From publieke...@gmail.com on 2015-02-02T03:00:22Z Was this patch applied to the main repository? In Spyder 2.3.2, pressing control-C or clicking the 'stop the current command' button still gives the same error message for a remote kernel: 'Kernel process is either remote or unspecified. Cannot interrupt' Would be great to have the possibility to interrupt remote kernels. |
From ccordoba12 on 2015-02-02T05:53:14Z External kernels can't be interrupted because of limitations in the IPython architecture. We'll see if we can do something about it in our next version, but it's a tricky issue. The patch you're referring to was applied a long time ago to interrupt kernels started by Spyder itself. |
From ccordoba12 on 2015-02-15T16:14:34Z Labels: -Component-IPython |
From ccordoba12 on 2012-06-04T20:42:46Z
This is a serious one: IPython doesn't let interrupt computations on remote kernels which is precisely what we're using to communicate with the variable explorer.
Fortunately the widget has a 'custom_interrupt' attribute that (hopefully) we could use to send the right signal to the right kernel. See: https://github.com/ipython/ipython/blob/1170c58b456d80fe1c81b24fd4728181c1d94b4d/IPython/frontend/qt/console/frontend_widget.py#L561 and the necessary signal here: https://github.com/ipython/ipython/blob/4b8de0203d2eec87c2d05c3521df8af3365f73a4/IPython/zmq/kernelmanager.py#L925
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1078
The text was updated successfully, but these errors were encountered: