On Sat, Apr 12, 2008 at 09:58:28AM -0700, Cliff Wells wrote: > On Sat, 2008-04-12 at 12:19 -0400, Phillip J. Eby wrote: > > At 09:07 PM 4/11/2008 -0700, Cliff Wells wrote:
> > >It seems the correct solution to this is to use "#!/usr/bin/env > > >python" (or rather, evaluate `which env` to account for some systems > > >which have /bin/env rather that /usr/bin/env) which allows the sys admin > > >to override the Python binary much more easily. > > No, it isn't the correct solution. The correct solution is to re-run > > easy_install on the target -- it will leave the existing installed > > code in place, but regenerate the scripts with headers pointing to > > the currently-in-use Python. > This is good to know, but still not as good as using env and the reason > is simple: every Unix user on the planet knows the env solution and what > it means if they see it in a script (they can override using PATH). The > same cannot be said for the above. +1. Gaƫl _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig