On Wed, Dec 3, 2008 at 5:04 PM, tfer <[EMAIL PROTECTED]> wrote: > looked at the extensions setup.py file, does not have the ILeo module > in the module list > so setup does not actually add this module.
Ok, it's a bug. setupegg.py develop works anyway. >> I use setuptools for this. >> >> run "setupegg.py develop" (nstead of install), and you can always pull >> to the dir without even installing. >> > > Is this what you are alluding to: > pull a copy of the developement trunk to some out of $PATH repository > directory > cd to that directory and invoke: > python setupegg.py develop > so the "egg" gets built but not installed in the local directory by > setuptools? An 'egg link' file is created, while the files exist in local dir. > I haven't located info on this "develop" switch, is it in setuptools > or specific to Ipython's setupegg.py file? setuptools. > do you then keep updating this repository and running say, > easy_install from the local directory to keep you Ipython current? No, just do "bzr pull" and your ipython stays current (no need for easy_install, setup.py, whatever after the first time). You need to delete old ipython's from site-packages so they don't get confused with the development version. -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
