Iirc, ipy_leo is leo 'helpers' that you load from ipython (as ipython plugin), and ipython.py is a leo plugin that enables the ipython bridge. Having them be separate seems natural to me, and users only know about ipython.py. On Apr 1, 2012 2:29 AM, "Edward K. Ream" <edream...@gmail.com> wrote:
> 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. > > Ville, do have any comments? > > Edward > > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To post to this group, send email to leo-editor@googlegroups.com. > To unsubscribe from this group, send email to > leo-editor+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/leo-editor?hl=en. > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
