Just to add my $0.02 for completeness:
People use:
#!/usr/bin/env python
so that the script will work on any system with a python on the PATH,
whether it's in /usr/bin or /usr/local/bin or wherever else.
Particularly on Linux systems, python gets installed different places
depending on
On 8/31/05, Robert Kern [EMAIL PROTECTED] wrote:
It selects the first executable named python in the PATH. The shebang
line requires an explicit executable. For example,
Thanks, All. I've got it all working now, with your help. I'm glad to
see that the Python Mac community is as beyond-the-call
On 8/30/05, Bob Ippolito [EMAIL PROTECTED] wrote:
I think that installer is broken, compile from source.
appscript does not have an installer for 2.4, you'll have to compile
it and its 5 or 6 dependencies.
Thanks. I've grabbed source copies of all of these, and I'll have a
bash with them this
Hi -
Or I can just invoke the /usr/local/bin version explicitly, yes? Seems
to work...
How do I specify that in a shebang line? I tried #!/usr/local/bin
python, but I got a bad interpreter: Permission denied error
message.
Did you mean #! /usr/local/bin/python
or #!
Complete and utter Mac newbie here - be gentle with me!
Hi, all. I've downloaded and installed MacPython 2.4.1 from
undefined.org. It installed happily enough, and seems to run fine. But
when I attempt to install PyObjC (from
pyobjc-1.3.7-py2.4-macosx10.4.zip) it says that it requires Python
2.4.
On Aug 30, 2005, at 9:53 AM, Simon Brunning wrote:
Complete and utter Mac newbie here - be gentle with me!
Hi, all. I've downloaded and installed MacPython 2.4.1 from
undefined.org. It installed happily enough, and seems to run fine. But
when I attempt to install PyObjC (from
Hi -
On 8/30/05, Simon Brunning [EMAIL PROTECTED] wrote:
I think that may be something to do with the fact that the original
version of Python that came with the machine is still 'in charge'.
Starting Python on the command line gives me version 2.3.5 - and when
I installed appscript, it
