Yes, I’ve used papermill, nbformat, and Jupytext to go from a templated Python to a notebook. Lately, mostly tended towards the latter two as I find papermill seems to introduce unnecessary cruft.
Example:
- Go here and launch a session with ‘
launch binder’. Then in the session that comes up, pick the second notebook listed under ‘Available Notebooks’ and look at that and the underlying code. I wrapped it in snakemake; of course, you don’t have to do that.
You can do this a couple of ways. The simplest is jupyter nbconvert --to html --no-input pointed at a notebook file. However, I found better was to build a script that made a nbconvert preprocessor that respects the source_hidden=true metadata in a cell so I could collapse all cells and have them come out absent in the HTML or I could just collapse selected ones and still have some code cells present in the output HTML, if I wanted. As part of this script, I made custom CSS and JavaScript to style the collapsed cells in the resulting HTML. I made a repo with a my binder-launchable session demonstrating this pipeline in a generic way here. Basically, it is a very customized version of the advice in the last paragraph here. It takes a demonstration notebook that has both collapsed and uncollapsed code cells and makes a report out of it in HTML format. The HTML will respect the collapsed and uncollapsed cells. The idea being that HTML can then be printed from your favorite browser.