[IPython-dev] IPython1 parallel questions

Brian Granger ellisonbg.net at gmail.com
Mon Dec 18 18:21:29 EST 2006

This is absolutely something we have on our radar, but we don't have
it implemented yet.  It is especially complicated if commandX()
happens to run C/C++ code.  Then the signal handlers in Python won't
do a thing.  To get that to work, you need:

1.  Another process on the same machine that send OS level signals.

2.  The author of the C-code must use a macro to install the right
signal handlers.

This becomes even more complicated if MPI is involved.  This that
said, Fernando has thought quite a bit about this before and we plan
to eventually work on it.


On 12/18/06, Douglas Jones <dfj225 at gmail.com> wrote:
> Brian,
> Thank you for your responses, they have been very helpful.
> Another question that came up involves the termination of a running command.
> As an example, say that I do
> rc.executeAll('commandX()')
> and commandX happens to be a  long running command. Shortly after
> hiting enter, I realize using commandX was a mistake.
> Is there some way to halt the execution of commandX?
> Based on your description of how the engines operate, I suppose this
> currently isn't feasible. Have you considered creating a way to halt
> commands on the engine without destroying the state of the system? I
> think something like this would be useful for interactive computing
> with large datasets.
> Thank you,
> ~Doug

More information about the IPython-dev mailing list