On 12/2/05, Carsten Haese <[EMAIL PROTECTED]> wrote: > (3) assumes that whatever shell the user is running looks up the shebang > executable in the path, which bash, just to name one example, does not > do.
I think that was the answer I was looking for. So that "#!/usr/bin/env python" is more portable than "#! python" and that's probably why it worked for me with cygwin/bash but not for Klaus on whatever platform he used. > (2) and (1) require that you know where env and python live, > respectively, that's true, but env is likely to be found in an > OS-dependent standard location than python, so (2) is preferable. I agree. Only a very strange Unix-like installation would not have 'env' at '/usr/bin/env'. Many thanks to Klaus and Carsten for helping me find out why this convention is helpful/useful. Best regards, Adriano -- http://mail.python.org/mailman/listinfo/python-list
