> I'd rather not add .pth files by default. In the new bzr world I'm > often working on several different branches at once. Adding .pth > files could create some unintended results.
Maybe that could be prevented by using a .pth-file for each branch like leo-4-3-b1.pth, leo-4-3-1-b2.pth, etc. > > > 1) add a leo.pth file to /usr/lib/python2.5/site-packages that > > contains the line /usr/local/lib/leo > > 2) substitute all 'import leo.core.<whatever> as <whatever>' with > > 'import core.<whatever> as <whatever>' > > No way am I going to change imports from 'leo.core' to 'core'. The > present workflow assumes that I 'cd' to the top-level directory of a > branch. Well, that's _your_ work flow, but surely it does not have to be for other users of your software? Anyway, I'm just not an expert on the module-importing-machinery, and was surprised that my change of the import statement resulted in a working state. I understand from your statement that your work flow would break when applying this change. Would you care to explain me why that would be? (I apologise beforehand if this is basic Python knowledge) > > We have gone around and around with the linux install script. I'd > rather not change it at all unless absolutely required. > > Edward I appreciate that point of view. Cheers, Roger --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
