-
Notifications
You must be signed in to change notification settings - Fork 76
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
Support kernel interrupts #5
Comments
Hi @andystoneucl, thanks for your interest. I think the ability to interrupt the Matlab process is actually something that should go in |
Thanks. Make sense that it belongs in Hopefully it's possible to implement somehow - I don't know if the mechanics of how Jupyter connects to Matlab is fundamentally different to how it connects to Python, but the interrupt button works for the regular Python kernel. |
FWIW the native kernel seems to support this with no problem (crosspost to #48). |
I have a solution but there's a separate bug in wurlitzer that affects long outputs (see above), so that'll depend on it being fixed. Edit: pushed the fix to master, despite the continuing issue with wurlitzer. |
Vendorized wurlitzer with a fix. Lack of windows support remains an issue; see #59. |
Very promising project, I love being able to use Matlab through Jupyter, but it appears that the 'interrupt kernel' button doesn't do anything (on Windows 8.1 at least).
If I forget a semicolon in a big Matlab loop then I can hit ctrl+C in the normal Matlab command window to stop the loop (otherwise it takes forever writing massive quantities of output to the screen). Without the interrupt kernel option the only options you are left with are waiting for it to eventually finish or killing the whole kernel - which is undesirable if you then have to re-run loads of slow stuff to get back to the same point.
Had a quick look at the ipython/Jupyter documentation but couldn't see where kernel interrupts might need to be implemented.
The text was updated successfully, but these errors were encountered: