Skip to content


Problems with Control-C stopping ipcluster on Windows/Python2.6 #68

ipython opened this Issue · 3 comments

3 participants


Original Launchpad bug 515376:
Reported by: ellisonbg (Brian Granger).

When ipcluster is running and you hit Control-C, it should stop all of its child processes and then exit. On Windows, under Python 2.6, doing Control-C exits immediately and doesn't stop the child processes. When using the WinbHPC scheduler, these child processe are job.exe. When I add --log-level 10 to ipcluster and then retry, I see that it looks like the job.exe processes have already exited. This could be a tough one to track down and the problem could even be in Twisted.

IPython member

This will be resolved when we refactor ipcluster to use subprocess of Python 2.6.

IPython member

This is not a problem in the zmq newparallel code, and we won't fix it in Twisted.

@minrk minrk closed this
IPython member

IPython.kernel is removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.