[IPython-dev] Propagate errors with ipython nbconvert --execute?
Thomas Kluyver
takowl at gmail.com
Mon May 4 00:50:27 EDT 2015
Stop on error should be a configurable option.
On 3 May 2015 9:37 pm, "Andrew Gibiansky" <andrew.gibiansky at gmail.com>
wrote:
> What if you want to demonstrate in your notebook (or documentation) that
> particular behaviour causes an exception?
>
> -- Andrew
>
> On Sun, May 3, 2015 at 8:01 PM, Thomas Kluyver <takowl at gmail.com> wrote:
>
>> The main part of the repo split is done - there's still a few details
>> being worked out, but nbconvert now lives here:
>>
>> https://github.com/jupyter/jupyter_nbconvert
>>
>> PRs are welcome. We might rename the repository in the next couple of
>> days, but I don't think that should interfere with pull requests.
>>
>> Thomas
>>
>> On 3 May 2015 at 19:55, Maximilian Albert <maximilian.albert at gmail.com>
>> wrote:
>>
>>> Incidentally, I needed precisely this functionality for a project I'm
>>> currently working on (where I'm generating a bunch of analysis notebooks
>>> from a "template" notebook into which I inject a couple of
>>> analysis-specific cells). I have a PR for this locally, but wanted to hold
>>> off submitting it until the IPyhon repo split is over. Happy to submit it
>>> when that's done (btw, is there a rough ETA for it?), or leave it to
>>> tritemio who mentions in issue #8266 that he also has one.
>>>
>>> Cheers,
>>> Max
>>>
>>>
>>> 2015-05-04 3:41 GMT+01:00 Thomas Kluyver <takowl at gmail.com>:
>>>
>>>> This would be a valuable feature for someone to add.
>>>>
>>>> https://github.com/ipython/ipython/issues/8286
>>>>
>>>> On 3 May 2015 at 17:46, Michael Waskom <mwaskom at stanford.edu> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> ipython nbconvert has, of late, the --execute flag, which makes it
>>>>> handy to work with notebooks as documentation source without having to keep
>>>>> the output in a git repository.
>>>>>
>>>>> However, when invoked as specified in the version 3 release notes:
>>>>>
>>>>> ipython nbconvert --to notebook --inplace --execute my_notebook.ipynb
>>>>>
>>>>> the converter trundles right along past exceptions raised in the code
>>>>> blocks.
>>>>>
>>>>> It would be helpful if there were some option so that the executable
>>>>> would return with a nonzero error code when an exception was raised so
>>>>> problems more easily detected. Is that possible? I didn't see any obvious
>>>>> arguments to that flag when I looked at the help, but it's a complicated
>>>>> tool.
>>>>>
>>>>> Thanks!
>>>>> Michael
>>>>>
>>>>> _______________________________________________
>>>>> IPython-dev mailing list
>>>>> IPython-dev at scipy.org
>>>>> http://mail.scipy.org/mailman/listinfo/ipython-dev
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> IPython-dev mailing list
>>>> IPython-dev at scipy.org
>>>> http://mail.scipy.org/mailman/listinfo/ipython-dev
>>>>
>>>>
>>>
>>> _______________________________________________
>>> IPython-dev mailing list
>>> IPython-dev at scipy.org
>>> http://mail.scipy.org/mailman/listinfo/ipython-dev
>>>
>>>
>>
>> _______________________________________________
>> IPython-dev mailing list
>> IPython-dev at scipy.org
>> http://mail.scipy.org/mailman/listinfo/ipython-dev
>>
>>
>
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20150503/d03fa204/attachment.html>
More information about the IPython-dev
mailing list