[IPython-dev] ipython1 remote exceptions causing local crashes

Fernando Perez fperez.net at gmail.com
Tue Feb 20 17:05:36 EST 2007


On 2/20/07, Douglas Jones <dfj225 at gmail.com> wrote:

> Please forgive me if some of the issues I bring up have already been
> discussed or have already been addressed in the code, as I haven't
> been able to look through all of the new features and changes.
> For the project that I am working on, it seems that one of the big
> features is to use your cluster in an interactive manner. The "feel"
> of this for our current implementation is much like typing any other
> command into your python shell. Ipython1 goes a long way to providing
> the features to make this necessary.
> That said, it seems like an overreaction to have the user, more or
> less, ejected from their interactive session for what may have been a
> trivial mistake. I think one of the nice features of working
> interactively is that you are given a chance to fix the mistake and
> continue along with minimal fuss.


Ah! What you are mentionig is most definitely a bug, though.  Our
current expectation is that when you get a remote exception, you
should see an /exception/ in the local interactive shell, with a nice
traceback and all that.  But if you're actually getting dumped /out/
of ipython with a 'mail this crash report' message, that is a bug,
plain and simple.

Please do send us that crash report and whatever other details you
feel are relevant, and we'll try to hunt this one down ASAP.

Our intent is that the remote-enabled usage should feel very close to
the 'regular' ipython, so crashing out is definitely not a feature :)

Sorry that I misunderstood your original message.



More information about the IPython-dev mailing list