Re: Making Leo a package

2008-04-03 Thread Edward K. Ream
On Apr 2, 1:04 am, Ville M. Vainio [EMAIL PROTECTED] wrote: 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

Re: Making Leo a package

2008-04-03 Thread Terry Brown
On Thu, 3 Apr 2008 08:47:17 -0700 (PDT) Edward K. Ream [EMAIL PROTECTED] wrote: Actually, I should create an official branch. I just realized that what I have done (create a local branch of the trunk) is dangerous: if I forget and push that branch we will not be happy. Not sure if you've

Re: Making Leo a package

2008-04-02 Thread Ville M. Vainio
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. --

Re: @nosent file problem (was: Re: Making Leo a package)

2008-04-02 Thread Edward K. Ream
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

Re: Making Leo a package

2008-04-02 Thread Kent Tenney
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

Re: Making Leo a package

2008-04-01 Thread Terry Brown
On Tue, 1 Apr 2008 08:14:01 -0700 (PDT) Edward K. Ream [EMAIL PROTECTED] wrote: def finalize_options (self): # This method (and its pliant slaves, like 'finalize_unix()', # 'finalize_other()', and 'select_scheme()') is where the default Hmm, a formatted paragraph of narrative text

Re: Making Leo a package

2008-04-01 Thread Edward K. Ream
On Mar 31, 11:27 am, Edward K. Ream [EMAIL PROTECTED] wrote: 1. What directory structure must Leo have to make leo a package? An Aha: I can explore this question without using distutils at all. Indeed, I just manually copied the top-level leo directory to Python/ Lib/site-packages. I then

Re: Making Leo a package

2008-04-01 Thread Ville M. Vainio
On Tue, Apr 1, 2008 at 7:04 PM, Edward K. Ream [EMAIL PROTECTED] wrote: Now, after stepping through the code a few times, I have a much better feel for what the code is intending to do. I can return to the sources to look for clues. My first guess is that the atrociously- documented

Re: Making Leo a package

2008-04-01 Thread Kayvan A. Sylvan
On Tue, Apr 01, 2008 at 09:04:48AM -0700, Edward K. Ream wrote: P.S. The docs say it is possible to set os.environ['DISTUTILS_DEBUG'] = 'any-non-empty-string' in order to enable debugging. In fact, setting os.environ is non-trivial. Isn't this just a matter of doing this in Linux at the

Re: Making Leo a package

2008-04-01 Thread Kayvan A. Sylvan
On Tue, Apr 01, 2008 at 08:34:20PM +0300, Ville M. Vainio wrote: Or if you are using IPython with 'sh' profile (ipython -p sh), you can do %env DISTUTILS_DEBUG=t After that, all ipython sessions have that environment variable automatically. Cool! That's a cross-platform suggestion, then,

Re: Making Leo a package

2008-04-01 Thread Edward K. Ream
On Apr 1, 12:11 pm, Ville M. Vainio [EMAIL PROTECTED] wrote: On Tue, Apr 1, 2008 at 7:04 PM, Edward K. Ream [EMAIL PROTECTED] wrote: I don't think you should spend so much time with distutils - it kind of expects that it's used as it's supposed to, and fooling around too much can cause

Re: Making Leo a package

2008-04-01 Thread Edward K. Ream
On Tue, Apr 1, 2008 at 12:46 PM, Edward K. Ream [EMAIL PROTECTED] wrote: I think your suggestion to change leo/src to leo/core is a good one. I suspect, though, that making Leo into a proper package, with 'core' and 'plugins' (etc.) subpackages, probably should wait until 4.4.8 final. Would

Re: Making Leo a package

2008-04-01 Thread Ville M. Vainio
On Tue, Apr 1, 2008 at 8:46 PM, Edward K. Ream [EMAIL PROTECTED] wrote: I think that setuptools is a much better bet: http://peak.telecommunity.com/DevCenter/setuptools Thanks for this reminder. I've looked at it in the past and it looked good. But then, don't users have to

Re: Making Leo a package

2008-04-01 Thread Ville M. Vainio
On Tue, Apr 1, 2008 at 9:04 PM, Kayvan A. Sylvan [EMAIL PROTECTED] wrote: Although I can't figure out where ipython stored the macro in my Windows box. :-) Ville, can you point me to the right file? They are stored in a pickleshare database that IPython uses for all persistent stuff.

@nosent file problem (was: Re: Making Leo a package)

2008-04-01 Thread Kayvan A. Sylvan
On Tue, Apr 01, 2008 at 09:14:56PM +0300, Ville M. Vainio wrote: They are stored in a pickleshare database that IPython uses for all persistent stuff. Explore the ~/_ipython/db directory. Observant reader may guess that it contains pickles ;-). If you want the contents of the database in a

Re: @nosent file problem (was: Re: Making Leo a package)

2008-04-01 Thread Kayvan A. Sylvan
On Tue, Apr 01, 2008 at 03:34:28PM -0700, Kayvan A. Sylvan wrote: This led me to try a test case: A simple file with a single node (H denotes the headline and B denotes the body below): H: @nosent foo B: Direct text in body pane. Aha! Changing the above file to this fixes the issue: H: