| > Alternatively, if you don't care about cell outputs then Jupytext[5] to sync .ipynb JSON to markdown Notice that using markdown is a possibility for jupytext, but not the only one. More interestingly, you can also store your notebooks as plain python files, whose comments are interpreted as the markdown cells of the notebook. This is very useful, and not only for version control: if your notebooks are python files they can be executed easily in CI or by third parties just by launching the interpreter. No need even of the jupyterlab dependency. With some care, you can craft a single python file "foo.py" that can be used at the same time as 1. an executable command-line program (that happens to be written in python) 2. an importable python module 3. a jupyter notebook (to open it you need the jupytext extension of jupyter) 4. the documentation with auto-generated figures, convertible to html or to pdf using "jupyter nbconvert --execute" 5. a regular .ipynb if for some reason you want to distribute the outputs in a re-executable format For small simple projects, to showcase, describe and illustrate an independent algorithm, we have found this structure invaluable. |