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

Closed
ipython opened this Issue May 10, 2010 · 3 comments

Comments

Projects
None yet
3 participants
@ghost
Collaborator

ghost commented May 10, 2010

Original Launchpad bug 515376: https://bugs.launchpad.net/ipython/+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.

@ellisonbg

This comment has been minimized.

Show comment
Hide comment
@ellisonbg

ellisonbg Dec 9, 2010

Member

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

Member

ellisonbg commented Dec 9, 2010

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

@minrk

This comment has been minimized.

Show comment
Hide comment
@minrk

minrk Mar 23, 2011

Member

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

Member

minrk commented Mar 23, 2011

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

@minrk minrk closed this Mar 23, 2011

@ellisonbg

This comment has been minimized.

Show comment
Hide comment
@ellisonbg

ellisonbg Mar 31, 2011

Member

IPython.kernel is removed.

Member

ellisonbg commented Mar 31, 2011

IPython.kernel is removed.

minrk pushed a commit to minrk/ipython that referenced this issue Jul 1, 2013

Merge pull request #68 from scopatz/master
Fix for minor issue with upstream docutils.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment