4 ms·

Have you worked with Jupyter notebooks and git? It's a literally true statement :D and quite a struggle for many of us

• cycomanic 4y ago
  It's the wrong way around though, Jupyter notebooks break a git work flow. I think the fault here is completely with the design of the Jupyter notebook file format (and the way editors save to it). I think it's quite unfortunate that they did not consider that the format would integrate well with version control systems when first designing ipython notebooks.
  • fumeux_fume 4y ago
    Nah man, you got it backwards. Git still works just fine while my notebooks are definitely broken. Not here to play the blame game, just trying to relate the practical results.
• xcambar 4y ago
  If you leave git diffs in your files, whether Jupyter notebooks or otherwise, and run/compile them... They will break. If you give me a counter example, good for you, but my statement holds true 99%.
  • jsweojtj 4y ago
    You state in the top level comment that this claim stains the article: "Stating that git breaks Jupyter notebooks is quite a flex." But you are saying here: "If you leave git diffs in your files, whether Jupyter notebooks or otherwise, and run/compile them... They will break." Have you changed your mind in this thread? Or what's your objection?
    • xcambar 4y ago
      I'm suggesting that git only breaks Jupyter notebooks (or anything else) if you do not know what to expect from git. But if you don't know that git modifies files when conflicts, then you're an interesting and rather unexpected audience, I assume. Meaning that for the typical git user, meaning, knowing about git diffs, the behavior is expected hence not broken. The files end up in an expected broken state, but git does not break them per se. If you still disagree, let's just settle that we disagree and be done with it.