> This Engineering Notebook post describes a breakthrough that will radically simply #4117 <https://github.com/leo-editor/leo-editor/issues/4117> support jupytext.
I elided some important details: > When Leo *reads *an @jupytext x node, Leo will use jupytext to re-create that node and all its descendants from x.ipynb. Recreating the node implies using jupytext to create a *temporary *.py file. But this file will exist only as a string. It will never become a real external file: I have to say @jupytext is an amazing idea. I wonder if it would be better to let the user choose whether to write to an external file or not? Considering the purpose of jupytext: > Have you always wished Jupyter notebooks were plain text documents? Wished you could edit them in your favorite IDE? And get clear and meaningful diffs when doing version control? Then, Jupytext may well be the tool you’re looking for! If we just save it in Leo as string, we may lose this advantage. Of course, it seems that the logic is more complicated. In this case, @jupytext x.py @jupytext x.ipynb @jupytext x will make a difference. I don’t have a clear preference for this idea, just an idea. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/leo-editor/b79b16b6-541e-4fc7-9c53-2db4330e05d2n%40googlegroups.com.
