Can not stop "ipython kernel" on windows

[jstenar]

when running the "ipython kernel" command on windows I can not stop the kernel process. Ctrl-c does not stop the process like it does when using "ipython notebook". I have to kill the process manually using the process explorer.

[minrk]

Not windows specific, and also not so much a bug as an annoying feature. If we allowed sigint to terminate a kernel, then interrupting it from the notebook or qtconsole would occasionally appear as a crash.

[joonro]

I am not sure if this is the same problem I have. I started a kernel with IPython.embed_kernel(), and I cannot kill it. I'm using linux and ctrl + c does not work.

[minrk]

^C should not terminate the process, because ^C must be interpreted as a regular sigint and raise KeyboardInterrupt in user code. We don't want ^C to kill the kernel, because then if a user tries to interrupt their own code, the kernel will die. We used to allow ^C to kill the kernel while user code was not running, but this still allowed accidental kernel shutdown if you tried to interrupt your own code, but ended up sending the signal after your code finished. The only sensible answer is for kernels to not be killed by ^C.

We could, however, change the ipython kernel entry point to, instead of launching the kernel directly, start a minimal KernelManager, which in turn starts the actual Kernel. If we did this, then you could interrupt the KernelManager directly with ^C, which would in turn cleanup the kernel.

[idbrii]

Is the only way to kill ipython kernel to send it a sigterm?

[minrk]

@pydave or ask it to shutdown from a frontend.

[ivanov]

arg! i just spent a half hour trying to figure out where i should make some changes to make this work... :\

[lithp]

@minrk I've tried my best to google but can't seem to find it. How do you ask it to shutdown from a frontend?

[minrk]

If it's a terminal client, you can type exit. Or you can connect a KernelClient object, and call client.shutdown()

[franco2ke]

@minrk thanks for the explanation. However now that you have shown why ctrl-c does not work, how do I stop the script?

[franco2ke]

Ok! My bad. I just found out because I had set 'debug = True' it was reloading my script continuously, that's why I wasn't able to stop it. Ctrl-c worked for me, on the regular console

[cerodell]

I'm having an issue connecting to an existing kernel on a remote server while using spyder on my local machine.

I am running spyder 3.3.6, I have installed miniconda and spyder-kernels on the remote server.

I launch python -m spyder_kernels.console on the remote server

Then on my local machine running spyder, I go the "gear" tab in the iPython console and click "connect to an existing kernel".

I check the "This is a remote kernel (VIA SSH)"
Type in hostname and password...then nothing..... won't connect.

Where am I going wrong?

Thank you in advance for your help!!!!!!!

[MrMino]

@Ambuj-Choudha this is a thread from 10 years ago, and it's unrelated to your issue. Please create a new issue in appropriate tracker from Jupyter org or in ipykernel