On Sat, Oct 19, 2024 at 11:21 PM HaveF HaveF <[email protected]> wrote:
Honestly, it would be great if Leo was used to organize jupyter, but I > think this problem is too complicated. > Maintainability may also become a big problem in the future. > I agree. Your remarks here came at the perfect time. I thought of them often while writing my latest post <https://groups.google.com/g/leo-editor/c/6n_mS9W2p1s/m/EV_fLLRLAQAJ>. I usually synchronize the source code and ipynb through > https://github.com/mwouts/jupytext, and then use Leo to organize the > source code. > Thanks for the link! jupytext supports the conclusion that IPython needs no help from Leo. > Of course, my whole process seems to be a little troublesome, but in > general, the complexity is low, and if there is a problem, it can be easily > found. > It was a mistake to think that Leo gains from working closely with IPython. Thanks for helping us all abandon this mistaken idea! Edward -- 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/CAMF8tS0aC9q0gszuZ%3D0dqve-d%2BNuNakwpLMwL%3DY1nVwVp%2Bbiyg%40mail.gmail.com.
