Debug / Skip cell tag about papermill HOT 4 CLOSED

Would that break the perception of a linear flow of a notebook run by papermill?

I guess this kind of leads towards a desire to stitch notebooks together in parts rather than always having the whole document. It's useful to have them together when authoring, when run as a job though you want a limited view I suppose?

from papermill.

What about supporting something like papermill step1.ipynb step2.ipynb outputs/ which then generates outputs/combined.ipynb? I'd rather compose notebooks on the command line than have annotations on cells to run/not run them.

One thing that is a bit clunky is passing complex objects (like fitted sklearn estimators) from notebook to notebook.

from papermill.

Has this feature been implemented? It'd be useful for debugging and/or Demo-ing a portion of the script at the end of the notebook, along with discussing design choices, sample data, analysis etc. When run on real data, the demo will be skipped. Right now I'm commenting the demo out and have to undo everytime I want to debug/show demo. Is it recommended that we keep 2 separate notebooks in this case? Keeping them up to date/coupled with each other can be a nuisance.

from papermill.

No, overall I think it's in the realm of potentially nice but complex. We've been leaning to keeping the repo simple over convenience features. One way you can control this today is to gate your demo cell with an if demo: wrapper and then set that in papermill -p demo on or at the top of the notebook when you want the demo activated.

I think I'm going to close this issue based on the trade-off discussions we've had in the past on related topics. If notebook format adopts a skip flag then we'll reopen this issue and address matching compatibility with other interfaces.

from papermill.