On Tue, Mar 31, 2020 at 8:19 AM Thomas Passin <[email protected]> wrote:
Thomas, seems like we agree on points 1 through 3. >> 4. In the (unlikely?) event that people want to use both Leo and jupyter, Leo can already import/export with jupyter > Here I differ. Leo cannot import/export anything Jupyter-ish but text nodes (and maybe code, I'm not sure). Are you talking about the .ipynb importer? > Not code execution results, and certainly not live interaction outputs. Are you sure? Don't .ipynb include everything? > That's why I posted that we would need to improve import/export to be able to properly share with non-Leo Jupyter folks. And even then, I don't see that we'd want to try to duplicate Jupyter's %-magic machinery. Better importers and exports are always welcome. > *No jupyter bridge needed* > > Yes! Exactly what I've been saying. Glad you see it too! > Oh good :-) > Although there is one scenario where it might be worthwhile using a > Jupyter kernel server. That would be if you wanted to execute a very long > calculation. You'd want to do that asynchronously, so you don't tie Leo up > waiting for it to finish, and Jupyter is designed to do that. > Does vr3 needs to support this? Couldn't users use popen to run calculations in a separate process? Or they could just use jupyter... 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/CAMF8tS0t29A692LqEZJ9Ud_eZ6xMYbF5mbtH30MofT9qWsSECQ%40mail.gmail.com.
