On Sun, 20 Feb 2011 19:52:14 PST, Me Pk said: > It turned out that the path for the python interpreter was set to /bin/env > and > it should have been /usr/bin/env.
Minor quibble - 'env' isn't the python interpreter. It's a wrapper that launches another program with a (possibly modified) set of environment variables. The usual use is to start off a shell script that uses (for instance) 'foobar' but you don't know where 'foobar' is installed. So you start it off as: #!/bin/env foobar Which will re-launch with the side effect of walking down $PATH looking for foobar, and running with whatever it finds, so you don't have to hard-code the path to foobar in the script.
pgpA4BYQJpKtI.pgp
Description: PGP signature
_______________________________________________ Flow-tools mailing list [email protected] http://mailman.splintered.net/mailman/listinfo/flow-tools
