-
Notifications
You must be signed in to change notification settings - Fork 14
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
Skipping cells during execution #37
Comments
I quickly skimmed through papermill's issue. looks like the community is in favor of a I think we can start with a simple implementation and improve it with community feedback: we can have the executor remove cells tagged with a specific tag and then execute the notebook. Would this work for you? Something like: ploomber-engine input.ipynb output.ipynb --remove-tagged-cells some-tag |
Maybe worth making it static so you don't need to pass it as a var each time..
And in |
I thought the same at the beginning, but since this will affect the execution flow, I think it's better to be explicit. |
We should do it explicitly, and then make sure we support an external file or an env variable so users don't have to repeat those multiple times. |
this is more work than just the remove feature so I think we should split in two issues. this one should only cover the cell removing part. |
Yeah, I'll reference a new issue. |
Yes, that works. Thank you. |
released in version 0.0.21! |
It would be good to have a way to skip certain cells during execution of jupyter notebooks.
My use case is that it is useful to have extra cells which might be useful for a developer while debugging or during interactive development - but shouldn't be run in regular runs.
But there are other scenarios discussed in the thread here:
nteract/papermill#429
The text was updated successfully, but these errors were encountered: