Reviewing Zeppelin and Jupyter Notebooks

stratosphere.dev

62 points·micheda··10 comments

There's also Iodide from Mozilla, which is pretty cool: https://alpha.iodide.io/

GitHub: https://github.com/iodide-project/iodide

Post explaining what it is: https://hacks.mozilla.org/2019/03/iodide-an-experimental-too...

It uses this markdown like file format: https://iodide-project.github.io/docs/jsmd/

There is also another tool called `pynb` (by the same author) that can be used to achieve human-readable format. The logic is a bit different there, since it generates a .py script file with markdown cells appearing as Python comments.

example diff: https://github.com/minireference/noBSLAnotebooks/commit/9005...

script: https://github.com/minireference/noBSLAnotebooks/blob/master...

pre-commit hook: https://github.com/minireference/noBSLAnotebooks/blob/master...

Hi Ivan, author here. Happy to read that pynb is useful! it can be used in a similar way (I used it also this way until I required support also for Zeppelin), however, it's limited to Jupyter and there's no Markdown support as you already pointed out.

Why wouldn't you just use org-mode and ob-ipython which lets you call out to jupyter kernels and have the results appear in your org file?

At least then you're dealing with diffs of plain text instead of json.

Emacs org mode definitely got this right. Storing everything as json feels like an ok choice, but there is a huge advantage to storing in the repo exactly what you review.

Converting notebooks to markdown is a fine idea (although you have to maintain both versions).

I built ReviewNB (https://www.reviewnb.com/) specifically to review Jupyter Notebooks on GitHub.

There's also jupytext: https://github.com/mwouts/jupytext

This works on Github: https://www.reviewnb.com/

Github formats Jupyter notebooks but not Zepplin, which for me is pretty much a slam dunk for jupyter.

Git + Jupyter notebooks is a disaster though.

Reply on news.ycombinator.com