Hello Edward, Am Sonntag, 1. April 2012 01:29:57 UTC+2 schrieb Edward K. Ream: > > In practice, the separation of code between the ipython.py plugin and > leo/external/ipy_leo.py is inconvenient for me and a bit confusing for > users. Indeed, Leo's --ipython command-line arg should be all that is > needed to create the ILeo bridge. > > I plan to fold the code in ipython.py and ipy_leo.py into a single > file. There seems to be no reason why this file should not be part of > Leo's core, say leoIPython.py. >
This question reminds me a bit of the times when the GUI-Issue was discussed. - Tk vs. Qt vs. ... Is it possible that this question could/ should be answered in the larger context of * what goes/ should go into Leo's core, * what is/ should always be a Leo plugin? With kind regards, Viktor -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/TMTzpZz6AxcJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
