[IPython-dev] Interrupting external kernel on Windows

[Doug Blank]

On Mon, May 12, 2014 at 1:49 PM, Thomas Kluyver <takowl at gmail.com> wrote:

> On 12 May 2014 05:58, Doug Blank <doug.blank at gmail.com> wrote:
>
>> Attempting to interrupt an executing command on a third-party kernel on
>> Windows. In fact, I went back to the simple_kernel [1], and I couldn't
>> interrupt it either on Windows. Is there some special handling for
>> interrupting a kernel on Windows?
>
>
> Yes, it appears there is. On Windows, we make a 'Win32 event' [1], which
> the kernel process listens for using some machinery in pyzmq [2]. It looks
> like the event number that the child process needs to listen for is
> currently passed to the kernel as a command line argument, which we can
> only do when we know we're starting an IPython kernel - we should probably
> pass it as an environment variable which any kernel can use.
>

Thanks for tracking that down! It would be good if the lack of a method of
signaling 3rd-party Window's kernels could be considered a bug, so that a
solution can be rolled into a IPython 2 update. Not being able to interrupt
a kernel is a major issue.

Started an item tracker here:
https://github.com/ipython/ipython/issues/5840

-Doug



>
> [1]
> https://github.com/ipython/ipython/blob/master/IPython/kernel/launcher.py#L186
> [2]
> https://github.com/ipython/ipython/blob/master/IPython/kernel/zmq/kernelapp.py#L164
>
> Thomas
>
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20140512/6ebc2b99/attachment.html>