That's very interesting. The Jupyter ecosystem is expanding so fast that there is always something new. I don't actually use Jupyter-* so I'm not in touch with it at all. I always think I should be using Jupyter but I don't do much work these days that would make much use of it.
On Sunday, October 20, 2024 at 9:35:32 AM UTC-4 [email protected] wrote: > Leo gains nothing by attempting to work closely with IPython. > > I agree with Edward that complex integration does not bring any benefits. > > If I imagine, the combination of Leo and Jupyter may only be a combination > at the file level. Maybe Leo will parse the ipynb file and turn it into > blocks, and then we can use Leo's outline feature to > deconstruct/organize/clone blocks at will. > After the new outline is formed and saved, then in JupyterLab, `reload > from disk` reads the new ipynb file. > > We all know that Leo's outline is unmatched✨✨✨ > > As I said before, for now, there is no such function, I use jupytext to > implement the above idea. > > ipynb files ----(jupytext)--> py files ----(import and organize by leo) > --> (modify py files from leo or any other editors) --> (reload from disk) > in jupyterlab --> (reset kernel and run all cells) > > > -- 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/5095fa12-a261-4938-99ea-ce96c94940a4n%40googlegroups.com.
