Forgive my imperfect understanding of this, but I think that the old
Leo-Ipython stuff worked by having the same python interpreter
instance running both leo and ipython shifting things of interest back
and forth through namespaces that either could look at.
While this still may be possible with
On Apr 2, 9:21 am, tfer tfethers...@aol.com wrote:
Forgive my imperfect understanding of this, but I think that the old
Leo-Ipython stuff worked by having the same python interpreter
instance running both leo and ipython shifting things of interest back
and forth through namespaces that
On Mon, 2 Apr 2012 08:32:40 -0700 (PDT)
Edward K. Ream edream...@gmail.com wrote:
Yes. zmq is exciting. Alas, I have not been able to build it either
on Windows or Ubuntu.
It's available as a package in the package management system for
Ubuntu. Unfortunately tfer said zmq in windows was
Unfortunately tfer said zmq in windows was hard, if that's
true, then that's a pain,
I have pyzmq working I think, or at least I was able to get ipython
notebook running on my computer last week (python 2.7). I believe I
just used `pip install pyzmq` and it was off to the races.
I was
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
On Sun, Apr 1, 2012 at 12:31 AM, Ville M. Vainio vivai...@gmail.com wrote:
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
On Apr 1, 6:34 am, Edward K. Ream edream...@gmail.com wrote:
Unless [there are technical objections] my plan is to merge both into Leo's
core.
Creating a new core file, say leoIPython.py will allow us to keep
ipy_leo.py and ipython.py unchanged during development of the new
IPython support
On Sun, Apr 1, 2012 at 7:31 AM, Edward K. Ream edream...@gmail.com wrote:
Hmm. Perhaps Leo will need a --legacy_ipython command-line arg.
A ridiculously bad idea ;-) The new IPython controller will determine
which version of IPython is in effect and act accordingly.
EKR
--
You received
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
