>> Alas, explicitly specifying the long path didn't work either. It
>> bombs on import of appscript:
Robert> Try
Robert> #!/usr/bin/env /usr/bin/pythonw
Cool! Works like a charm. Thanks...
Skip
___
Pythonmac-SIG maillist - Python
[EMAIL PROTECTED] wrote:
> >>> #!/usr/bin/pythonw
>
> Bob> Sounds like you're using OS X 10.3. It shipped with pythonw as a
> Bob> shell script, not an executable.
>
> skip> Yes, thanks. Shoulda thought to actually look at
> skip> /usr/bin/pythonw...
>
> Alas, explicitl
>>> #!/usr/bin/pythonw
Bob> Sounds like you're using OS X 10.3. It shipped with pythonw as a
Bob> shell script, not an executable.
skip> Yes, thanks. Shoulda thought to actually look at
skip> /usr/bin/pythonw...
Alas, explicitly specifying the long path didn't work eit
>> #!/usr/bin/pythonw
Bob> Sounds like you're using OS X 10.3. It shipped with pythonw as a
Bob> shell script, not an executable.
Yes, thanks. Shoulda thought to actually look at /usr/bin/pythonw...
Skip
___
Pythonmac-SIG maillist -
On Feb 9, 2006, at 8:07 PM, [EMAIL PROTECTED] wrote:
>
> I want to manipulate iCal from the command line. Thanks to
> appscript it
> looks like I'll be able to do what I want.
>
> I wrote a simple skeleton script:
>
> #!/usr/bin/pythonw
Sounds like you're using OS X 10.3. It shipped with
I want to manipulate iCal from the command line. Thanks to appscript it
looks like I'll be able to do what I want.
I wrote a simple skeleton script:
#!/usr/bin/pythonw
"""
%(prog)s - manipulate iCal
"""
import sys
import os
import getopt
from appscript import