/usr/bin/env: python: No such file or directory

Cliff Wells logiplexsoftware at earthlink.net
Thu Dec 20 14:04:48 EST 2001

On Thu, 20 Dec 2001 10:16:54 -0800
Chris Barker <chrishbarker at attbi.com> wrote:

> I suppose, if we all, as a community, start using:
> #!/use/bin/env python2.1
> Then the problem will be solved, at least on *nix...
> Then what do you do with a script that will run on either 1.5 or 2.0 or
> 2.1 ????? and you don't know which of these might be installed?

It seems reasonable that if your script requires a particular version of Python to append the version to the executable name (i.e. python2.1), and if your script doesn't care, then just use "python" which could be a symbolic link to the default python interpreter (much as redhat has it now).  It might be helpful if the python interpreter took a flag such as --required-version or --minimum-version so that a warning could be printed if the script requires a version different than what is available on the system.

Cliff Wells
Software Engineer
Logiplex Corporation (www.logiplex.net)
(503) 978-6726 x308
(800) 735-0555 x308

More information about the Python-list mailing list