On Sun, Apr 1, 2012 at 3:52 PM, Viktor Ransmayr
viktor.ransm...@gmail.com wrote:
I tried to install Leo 4.10 final from Sourceforge via
LeoSetup-4.10-final.exe. Since I have a bazaar-based Leo environment
up and running I tried to install this into a completely new separate
user account.
After
I think I understand the various issues and complexities well enough
to give a short summary of the present plan:
- Leo's support for IPython will always be enabled, provided that
ipython exists in sys.path. There will be no need to enable a
separate ipython plugin. The leoIPython module will
On Apr 2, 8:08 am, Edward K. Ream edream...@gmail.com wrote:
The leoIPython module will support both legacy and new-style IPython commands.
Oops. I meant to say legacy and new-style IPython API's, that is,
both IPython 0.11 and 0.12 API's.
EKR
--
You received this message because you are
On Apr 2, 8:08 am, Edward K. Ream edream...@gmail.com wrote:
The last two items imply that the only top-level names of the leoIPython
module will be class names.
The following may have to exist at the top level::
ileo_pre_prompt_hook, lee_f, leoref_f, lleo_f, lno_f and
lshadow_f.
These
On Apr 2, 8:26 am, Edward K. Ream edream...@gmail.com wrote:
These are functions that are supposed to have self as their first
argument. This is an IPython convention, iirc. I'll hide these if
that can be done conveniently, but the world won't end if they remain
top-level functions.
Well,
On Apr 2, 8:30 am, Edward K. Ream edream...@gmail.com wrote:
Well, that's not going to work. These functions use what used to be
the c global (module-level) variable. So what is likely to happen
is that theses top-level functions are going to redirect somehow to
c.ILeoCommands methods.
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 Apr 2, 8:43 am, Edward K. Ream edream...@gmail.com wrote:
That's enough speculation for now. It's time to get back to writing
real code.
Rev 5225 contains the new packaging. Everything is in leoIPython.py.
It's remarkable how the new GlobalIPythonManager class clarifies
matters. All the
Hello Edward,
Am Montag, 2. April 2012 14:50:35 UTC+2 schrieb Edward K. Ream:
I assume by LeoSetup Script you mean LeoSetup-4.10-final.exe.
Yes.
If this is done intentionally, what is the rationale for it.
It wasn't done intentionally. There may be a nsi option to get around
this
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
It was important to make 'c' easily available to the ipython prompr; that
way, you could easily use ipython to 'learn' leo interactively (by playing
with c and tab completion). I found this much easier then ctrl+b command
even.
On Apr 2, 2012 6:46 PM, Edward K. Ream edream...@gmail.com wrote:
On
Hello Edwards,
I upgraded my local Leo installation to rev. 5225. - When I restarted
Leo I received the following traceback:
log
D:\Users\Viktor Ransmayr\Documentsleo ./WL2012.leo
Traceback (most recent call last):
File D:\Branches\leo-editor\launchLeo.py, line 8, in module
On Mon, Apr 2, 2012 at 1:10 PM, Ville M. Vainio vivai...@gmail.com wrote:
It was important to make 'c' easily available to the ipython prompr; that
way, you could easily use ipython to 'learn' leo interactively (by playing
with c and tab completion). I found this much easier then ctrl+b
In original bridge, there was only one process within which both leo and
ipython resided.
With new ipython (+zeromq), you may be able to hook different front end
processes to the leo backend process. Or not, I lost the track at some
point.
Must desirable ui would probably be the ipython qt
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
Just to confirm - build 5225 doesn't launch and gives the same
messages.
I had to revert to build 5224.
Regards
Lewis
--
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
On Mon, Apr 2, 2012 at 2:03 PM, Viktor Ransmayr
viktor.ransm...@gmail.com wrote:
Hello Edwards,
I upgraded my local Leo installation to rev. 5225. - When I restarted
Leo I received the following traceback:
Sorry about that. I didn't realize how much testing was needed for
the new code.
Rev
18 matches
Mail list logo
