well thanks for all the info, gents, i appreciate it a lot !<br>sk<br><br><div><span class="gmail_quote">On 11/26/06, <b class="gmail_sendername">زياد بن عبدالعزيز الباتلي</b> <<a href="mailto:zamb@saudi.net.sa">zamb@saudi.net.sa
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">"john maclean" <<a href="mailto:jayeola@gmail.com">jayeola@gmail.com
</a>> On Sun, 26 Nov 2006 01:34:28 +0000<br>wrote:<br>> From what I can tell/remember, the first works in the *nix environment<br>> if python is in your $PATH, ...<br>Actually, no. The first will try to feed the script to the executable
<br>"/usr/bin/python". If that doesn't exist (or is not executable) it'll<br>fail.<br><br>> ...the latter will find python "somehere" on your system by looking at<br>> wher the executables should be.
<br>True, assuming there's "/usr/bin/env" on your system (and is executable)<br>and that "python" is found in your "$PATH" (and is executable).<br><br><br>The problem is that Python is not installed in the same place on all
<br>OSes! Some will install it under "/usr/local", others under "/opt".<br><br>The idea of "/usr/bin/env" is that it's always installed there (or it<br>should be!). So, you don't need to figure out where is python (or perl,
<br>ruby, make, sed, awk, or any other executable that "feeds" on<br>scripts/text files) installed as long as it's in your "$PATH".<br><br>(Of course, "env" have other uses. As long as I can tell, this is not
<br>the intended use of "env". See "info env" for more information, or<br>if you don't have "info" see the manual.)<br><br>Ziyad.<br></blockquote></div><br>