Hi Diez,
Thanks for your reply. I gave this a try too, but it doesn't seem to work either.
However, a gentleman just emailed me off-list recommending to use the full path to Python that is in /usr/local/bin. This is where Python 2.5 looks to be installed rather than Python 2.3 which is in /usr/bin. I ran the following code below and it works great!
Thank you all again for your thoughts and replies. I really appreciate it!!
Jay
Thanks for your reply. I gave this a try too, but it doesn't seem to work either.
However, a gentleman just emailed me off-list recommending to use the full path to Python that is in /usr/local/bin. This is where Python 2.5 looks to be installed rather than Python 2.3 which is in /usr/bin. I ran the following code below and it works great!
--------------------
set p to "#!/usr/bin/python
import sys
print sys.version[:3]"
set x to do shell script "/usr/local/bin/python -c \"" & p & "\""
return x
--------------------
set p to "#!/usr/bin/python
import sys
print sys.version[:3]"
set x to do shell script "/usr/local/bin/python -c \"" & p & "\""
return x
--------------------
Jay
I guess the shebang is simply ignored - the actual interpreter is
fetched from the "Python -c"-line.
>
It's a bit weird that there is Python with a capital P, but what happens
if you change that to Python2.5 for example?
>
Diez
fetched from the "Python -c"-line.
>
It's a bit weird that there is Python with a capital P, but what happens
if you change that to Python2.5 for example?
>
Diez