You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition to full jupyter-cache support, we should also probably allow for lightweight execution of notebooks at build time, so that users don't have to embed outputs with their notebooks if they wish for them to be in the docs.
We could do this with nbclient, I think the question is how to handle things like "known exceptions" etc.
A simple rubric to follow would be what nbsphinx does, and decide whether to execute a notebook top-to-bottom if it has no outputs in any cells.
The text was updated successfully, but these errors were encountered:
chrisjsewell
added a commit
to executablebooks/jupyter-cache
that referenced
this issue
Mar 13, 2020
We could do this with nbclient, I think the question is how to handle things like "known exceptions" etc.
Just to note, we should endeavour to make sure that the execution logic is consistent over jupyter-cache, jupyter-sphinx and myst-nb, e.g. how known execptions are handled.
In addition to full jupyter-cache support, we should also probably allow for lightweight execution of notebooks at build time, so that users don't have to embed outputs with their notebooks if they wish for them to be in the docs.
We could do this with nbclient, I think the question is how to handle things like "known exceptions" etc.
A simple rubric to follow would be what nbsphinx does, and decide whether to execute a notebook top-to-bottom if it has no outputs in any cells.
The text was updated successfully, but these errors were encountered: