On Sat, Mar 31, 2018 at 10:15 AM, Thomas Passin <tbp100...@gmail.com> wrote:
I think we can go one better ... that is, to be able to put Leo organizer > nodes between Jupyter nodes. > That should happen automatically when writing the jupyter file. Retaining "non-jupyter" nodes when reading jupyter files would be much harder. It's akin to the @persistence logic, which is not for the faint of heart. > Another thing to bear in mind is that jupyter is an ecosystem that is > evolving fast. > Right. However, we can expect the api's to change more slowly. > I strongly support trying to integrate with jupyter rather than to try to > re-create its functionality. > That's the idea. I'll be studying pyzo/jupyter code with exactly this goal in mind. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
