On Fri, 2008-04-11 at 17:03 -0700, Philip Jenvey wrote: > > On Apr 11, 2008, at 4:44 PM, Cliff Wells wrote: > > > > > Is there a particular reason paster uses > > > > #!/usr/bin/python > > > > rather than > > > > #!/usr/bin/env python > > > > Having an absolute path to a system directory prevents symlinking a > > different version of python in a user directory, ignores PATH, > > etc. In > > short, it seems the wrong thing to do on Unix. > > It actually does, but setuptools or distutils replaces shebangs to > point to the version of python used to install the script. setuptools > also installs a copy with the python version number appended, e.g. > paster-2.5. That might help with some of these situations -- > otherwise I'd recommend using virtualenv or buildout for a custom > python in a user directory.
Perhaps, except that I have a system with many sites on it that predates these tools (and actually uses the recommended setuptools way of doing things) and can't be easily upgraded to virtualenv or buildout. The method I've been using is documented here: http://peak.telecommunity.com/DevCenter/EasyInstall#administrator-installation I'd like to add, that except for this one problem I've encountered, it's worked quite well for a few years now. I see virtualenv as solving a problem that was already solved by setuptools itself quite some time ago. Regards, Cliff -- > Philip Jenvey > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
