More and more I am thinking that we should give up the idea of round-tripping between Leo and Jupyter. What you have written goes in that direction. Leo would be the primary authoring tool. From time to time a user can reload in Jupyter and see if the results are what was intended. That's how it works with Sphinx documents and I've been happy with it.
I think most sharing of Jupyter notebooks takes place using an HTML file which is read in a browser. I'm not sure how it's generated, but maybe an actual Jupyter client session wouldn't even be required. On Monday, October 21, 2024 at 9:44:35 AM UTC-4 [email protected] wrote: > >> With jupytext <https://jupytext.readthedocs.io/en/latest/>as an >> inspiration, Leo might *pair .ipynb with corresponding outline nodes*: >> >> - Update the paired outline node when the corresponding .ipynb file >> changes. >> - Write the paired .ipynb file when the corresponding outline node >> changes. >> >> The details of pairing .ipynb files with outline nodes are fuzzy. But >> surely this pairing is possible. >> >> I assume that Jupyter can update .ipynb files when they change externally. >> > > It would be great if this works. I wouldn't have to use jupytext as a > bridge. > > Also, as far as I know, jupyter is not able to detect external updates, > and can only be updated using `reload notebook from disk` in the File menu. > > > ref: https://github.com/mwouts/jupytext#paired-notebooks > > You can edit the .py version of the paired notebook, and get the edits > back in Jupyter by selecting *reload notebook from disk*. The outputs > will be reloaded from the .ipynb file, if it exists. The .ipynb version > will be updated or recreated the next time you save the notebook in Jupyter. > > > -- 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 on the web visit https://groups.google.com/d/msgid/leo-editor/3e05a182-0734-455e-8b2f-ee3c03f33c51n%40googlegroups.com.
