On Wed, Apr 2, 2008 at 2:38 AM, Edward K. Ream [EMAIL PROTECTED] wrote:
I'm not sure what the solution is. Possibly all Leo imports will have
to be changed from:
import leoX
to
import leo.core.x.
Yes. Fully qualified imports will be made mandatory in the future anyway, IIRC.
--
On Tue, Apr 1, 2008 at 6:57 PM, Kayvan A. Sylvan [EMAIL PROTECTED] wrote:
So the edge condition appears to be where I save the unmodified leo file
and the @nosent file is missing/removed. In that case, I suspect that the
save does nothing and so no @nosent file is generated.
The @nosent tree
On Mar 30, 10:34 am, Ville M. Vainio [EMAIL PROTECTED] wrote:
You currently need to do the following to embed leo in existing ipython
session:
import IPython.Shell
IPython.Shell.hijack_tk()
%run leo.py (in leo/leo/src)
When leo is installable as a package, this will be much simpler
On Wed, 2 Apr 2008 01:47:44 -0700 (PDT)
Nik [EMAIL PROTECTED] wrote:
I have the following strange problem with cleo plugin.
My cleo settings on nodes at depth 7 are not permenant.
Strange indeed, I'll look into it, thanks.
Cheers -Terry
You're welcome, although I suspect you're getting some placebo
effect ;-).
My speedups are aimed at situations where clones cause the former
allNodes_iter to explore a potentionally huge tree that produces no
further result. Here's instructins on how to create an outline that
will show a *lot*
On Wed, Apr 2, 2008 at 11:18 AM, Edward K. Ream [EMAIL PROTECTED] wrote:
On Wed, Apr 2, 2008 at 10:48 AM, Kent Tenney [EMAIL PROTECTED] wrote:
setuptools seems to be heading for the standard library in some form,
it's the future.
...
The promise of mastering buildouts is very
