3 ms·

The pros and cons of Jupytext are discussed in the linked post. It's a great approach, but wasn't sufficient for our needs -- so for us, at least, it didn't ful

by jph00 4y ago

The pros and cons of Jupytext are discussed in the linked post. It's a great approach, but wasn't sufficient for our needs -- so for us, at least, it didn't fully solve the Jupyter+git problem. Specifically, it doesn't handle the situation where you need cell outputs in version control -- since in that case, you still need the notebook, which results in all the usual problems occuring. With nbdev2, you don't need to think about anything or do anything special, and stuff like GitHub notebook rendering, nbviewer, ReviewNB, etc all just work. You just run a single command (`nb_install_hooks`) and that's it. Also, no-one has to install anything extra to view your notebooks, since they're stored in the regular notebook format.

cycomanic 4y ago
I'm not sure what your cell outputs are, but if you are doing plots or images inside your notebook, than I agree with the OP that it is generally not a good idea. You now store binary data inside your git repository (which sometimes just carries its own problems), but worse that binary data is mixed into your text diff. If you do a diff between two revisions where some figure changed you essentially will be swamped by the diff in the figure making it difficult to find what actually changed. Now tools like nbreview get around that, but now you're forcing everyone to use the same dev tools, and can't look at diffs any other way really.
- glenngillen 4y ago
  It’s been a while, but last time I needed to GitHub at least had really great tooling for diffs between versions of image files. > but now you’re fixing everyone to use the same dev tools No they’re not. You can continue using whatever approach you’re using. Attempting to shut down alternatives like this though could be seen as forcing everyone to accept whatever that status quo and lowest common denominator solution, even if their dev tools could support something better.

by jph00 4y ago

cycomanic 4y ago

I'm not sure what your cell outputs are, but if you are doing plots or images inside your notebook, than I agree with the OP that it is generally not a good idea. You now store binary data inside your git repository (which sometimes just carries its own problems), but worse that binary data is mixed into your text diff. If you do a diff between two revisions where some figure changed you essentially will be swamped by the diff in the figure making it difficult to find what actually changed. Now tools like nbreview get around that, but now you're forcing everyone to use the same dev tools, and can't look at diffs any other way really.

glenngillen 4y ago
It’s been a while, but last time I needed to GitHub at least had really great tooling for diffs between versions of image files. > but now you’re fixing everyone to use the same dev tools No they’re not. You can continue using whatever approach you’re using. Attempting to shut down alternatives like this though could be seen as forcing everyone to accept whatever that status quo and lowest common denominator solution, even if their dev tools could support something better.