> although how do you add extra command line options?

$ ./python-and-bash-with-options.sh
['ARG!']
noland@swat:~$ cat python-and-bash-with-options.sh
#!/bin/bash
/usr/bin/python - 'ARG!'< 
@dubek,
That's a novel idea and I think it would work if env supported it, whether variables are expanded or not.
> I’m not sure that variable substitution would have worked inside the shebang line, even if we solve somehow problem
If I remember correctly, that entire line gets passed into the kernel.
I am going to look at this some more.

Brock

#!/usr/bin/env LD_LIBRARY_PATH=/home/noland/oracle-lib:$LD_LIBRARY_PATH /usr/bin/python

But it doesn’t work, because:

a. shebang lines are seperated into TWO (and only two) arguments —
1. the program to run (/usr/bin/env)
2. the rest of the line, given as a single argument the to program.
So in this case, the shell (or whomever is dealing with these shebang lines, I think you wrote on that once) tries to find a command named “LD_LIBRARY_PATH=/home/noland/oracle-lib:$LD_LIBRARY_PATH /usr/bin/python”, which doesn’t exist.

b. I’m not sure that variable substitution would have worked inside the shebang line, even if we solve somehow problem a. If you need to add something to an existing environment variable, you must have variable substitution, I guess.

Instead I used bashes multiline single quoted string feature to wrap my python source that I used double quoted strings in:

Python -c ‘
# python “source” “”"here”"”
‘

Your way seems better, although how do you add extra command line options?

- Paddy.