On Tue, Apr 1, 2008 at 12:46 PM, Edward K. Ream <[EMAIL PROTECTED]> wrote: > > 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 problems later on (e.g. in different platforms). > > I agree. > > > > 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 install setuptools first?
setuptools seems to be heading for the standard library in some form, it's the future. I've been trying to figure out buildouts http://pypi.python.org/pypi/zc.buildout/1.0.1 buildouts aim to be a comprehensive solution to the headache of managing software configuration. Given their scope, understanding how they work is a headache. A buildout is an umbrella over packages, eggs, scripts, commands ... most anything. A single buildout.cfg file can specify how to install a complex software environment repeatably. A buildout.cfg file could install an isolated instance of Leo, Ipython and winpdb with all the hooks in place, ready to go. That sort of thing. Again, I find the doc very difficult, mostly examples. I'm having trouble extrapolating from the examples. The promise of mastering buildouts is very compelling though. They have _lots_ of momentum. Thanks, Kent > > Actually, I'm starting to think that the whole "official release" > business is so "last year" :-) I'm tempted just to "release" leo on > bzr. > > > > > Also, if you want to debug it, there's a much better chance of getting > > your code/feature requests in. > > Oh, I have little interest in actually debugging or changing other > people's code--but the debugging attitude can be very liberating. > > > > > > Duh! leo.__init__.py is not sufficient to start Leo! > > > > You have to do: > > > > import leo.src.leo > > > > leo.src.leo.start() # EKR: should be leo.src.leo.run() > > leo.src.leo.run() fails: g.app isn't defined in the plugins. No doubt > this is a subtle import problem. At least I'm debugging my own > code :-) > > 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 that be a hardship for you, Ville? > > > > And indeed, you don't even have to copy the files to site-packages; > > you can try creating a "launchleo.py" script in leo root folder, and > > see what you have to do there to get going. Kind of like the > > ipython.py in the IPython source distribution root directory. > > setuptools also supports "python setup.py develop", which acts like > > the package is in site-packages, even if it isn't. > > Interesting. Again, copying leo by hand to site-packages was just an > experiment. It succeeded :-) > > Well, my head is spinning with all the options. > > What do people think about requiring bzr to get Leo. Is that too > leading edge? > > Edward > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
