4 ms·
Jupyter+Git has no problem. The problem is Jupyter notebooks+Git. The solution is use Jupyter, but not Jupyter notebooks.
by sdfghswe 3y ago
Jupyter+Git has no problem.
The problem is Jupyter notebooks+Git.
The solution is use Jupyter, but not Jupyter notebooks.
- SpriglyElixir12 3y agoWhat is the difference between the two? Googling it shows some comparisons between jupyter lab vs notebook but I can't find anything on plain jupyter.
- sdfghswe 3y agoJupyter is the protocol to communicate between a frontend and a backend. Jupyter notebooks is an interactive notebook that implements that protocol. Do you know what also implements the protocol? VS Code. And doesn't have any of the stupid problems that the Jupyter notebooks do.
- Noumenon72 3y agoAre you saying that VS Code also lets you do all of the "Run just this cell" that notebooks do?
- sdfghswe 3y agoYes. In VS Code if you do as below: #%% print("my python print") #%% Then you can run it as a cell. Crucially however, note that those delimiters are ALSO valid python code. So you just version as with everything else.
- jph00 3y agoThere isn’t a problem any more with notebooks and git because nbdev now provides a merge driver. So it’s fine to use notebooks with git now.
- esafak 3y agoThanks, but this is a bit pedantic. For most people Jupyter is the notebook. You could just as well call the other one the "Jupyter protocol".
- sdfghswe 3y agoIt's not pedantic, it's a huge difference. If I said "the problem is now solved, just use VS Code", most people would say "but that's not jupyter, i need the interactivity aspect", not realizing that VS Code is just as interactive (thank to jupyter).