> [EMAIL PROTECTED]> wrote: > > I haven't tested this, but for me, building a symbolic link into the > > python directory: > > > sudo ln -s /usr/local/lib/leo/ /usr/local/lib/python2.5/site-packages/ > > > made the message > > > Traceback (most recent call last): > > File "/usr/local/lib/leo/core/runLeo.py", line 464, in <module> > > run() > > File "/usr/local/lib/leo/core/runLeo.py", line 69, in run > > import leo.core.leoGlobals as leoGlobals > > ImportError: No module named leo.core.leoGlobals > > > disappear. > > Thanks for this tip. I'll find a place for it somewhere :-)
With me the error message disappeared as well. So why not find a place for it in the install script? :-) Only thing is that creating soft links on MS Windows is quite difficult (one has to use junctions, don't know if this is true for Vista also). I thought that placing a file called leo.pth in the site-packages directory would have the same, but platform-independent, effect as creating the soft link. It should contain a line with the directory of leo, like /usr/local/lib/leo. When I do this and start up a python session, sys.path shows that /usr/local/lib/leo is appended to the path. Unfortunately, I still get the error message when I start up leo from an arbitrary directory (i.e. not the directory being /leo that contains the core/ and other directories). Adding the line /usr/local/lib/leo/core to leo.pth also does not seem to help. Any hints? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
