It doesn't seem like Spyder is doing anything that Leo couldn't do. There may be a good reason that Spyder handles kernels externally, it might be the only reasonable way to get mulitple IPython kernels running.
All of that said it's going to take me quite of bit of study of Leo and IPython to get anything out "to the public". I simply don't have enough understanding of how IPython works to do anything other than hacking up chunks of code and hoping something works (which surprisingly it kind of did in this case). This will probably be a longer term project for me and in the meantime I'll be content with using ILeo (especially with the bufix). On Thursday, April 30, 2015 at 5:36:43 AM UTC-4, Peter Mills wrote: > > I've done a bit of looking at Spyder myself with similar ideas. However, > Spyder's IPython console uses an external IPython kernel, so it would be > impossible(?) to access Leo's innards using this technique. In fact, I > haven't been able to find a way to have both the GUI of IPython QtConsole > and the kernel running within another application. It seems (from the > IPython documentation) that you can have one or the other but not both. > > Having said that, I know that Spyder manages to send blocks of code (from > the editor) to the IPython kernel to execute. This could be useful for > executing code from nodes, so long as there isn't a need to access the Leo > node tree from the IPython kernel. > > Good luck with your study of Spyder/ILeo! > -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
