Hello

Sorry if this has been discussed before, my search did not find it.
My questions is if I should use
  #!/usr/bin/env python
as the shebang line in a portable and open python script and if it does help with portability and usage.

First, can one not find /usr/bin/python in any standard system, at least as much as /usr/bin/env can be found ?

Then, supposing /usr/bin/env is better than /usr/bin/python and I use it, is it not the case that many editors and code analysing programs, that want to know the script language for syntax highlighting, code completion, tags and source code browsing, etc, will loose their functionality because of this shebang line ? Is this not a good general reason to use the old one ?

Now I know env is POSIX standard utility, and python is not, and maybe that could be reason enough, but are there any other issues involved with using /usr/bin/env ?

Thank you
Timothy Madden
--
http://mail.python.org/mailman/listinfo/python-list

Reply via email to