Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "Cell -> Run All Keep Going" for notebooks #2626

Closed
cdeil opened this issue Nov 28, 2012 · 3 comments
Closed

Add "Cell -> Run All Keep Going" for notebooks #2626

cdeil opened this issue Nov 28, 2012 · 3 comments
Milestone

Comments

@cdeil
Copy link

cdeil commented Nov 28, 2012

I have this example notebook where I explain Python and IPython, and some of the examples demonstrate exceptions.

Now I have the problem that "Run All" stops on the first exception, but in this case I would like to going even if exceptions occur.

Would it be possible to add this possibility?

Here's an example demonstrating the current behaviour:
https://gist.github.com/4161224
http://nbviewer.ipython.org/4161224/

@pleabargain
Copy link

I'm not sure if this will do the trick... but how about:
http://ipython.org/ipython-doc/stable/interactive/tips.html

Use IPython to present interactive demos¶
Use the IPython.lib.demo.Demo class to load any Python script as an interactive demo. With a minimal amount of simple markup, you can control the execution of the script, stopping as needed. See here for more.

and I didn't know about the nbviewer! Very cool that!

@Carreau
Copy link
Member

Carreau commented Nov 28, 2012

Would it be possible to add this possibility?

I'm not quite sure it is a good idea, nonetheless, you could wrap the example in try/except and display the traceback by yourself, eventually using IPython helper functions.

I think there might be a discussion about some kind of magic that does it on the list.

Otherwise you could listen to Js event to submit cell n+1 only when cell n is done.

I'll wait for other dev to give their thought, but I'm -1 on integrating it by default.

@minrk
Copy link
Member

minrk commented Jan 20, 2013

Closing as duplicate of #1977.

@minrk minrk closed this as completed Jan 20, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants