In article <[EMAIL PROTECTED]>,
tom wible <[EMAIL PROTECTED]> wrote:
> btw, i figured out why i wasn't getting any mail from crontab: no
> output...d'oh!-} but i can't figure out how to get useful info out:
> >>> print
> app(u'/Applications/EyeTV.app').window[its.name.beginswith('EyeTV')].close
thanx to all who replied...version control is a major issue in all s/w dev...
i'm solving my problem w/ #!/usr/local/bin/python
btw, i figured out why i wasn't getting any mail from crontab: no
output...d'oh!-} but i can't figure out how to get useful info out:
>>> print
app(u'/Applications/E
On 29/02/2008, at 14:21, Christopher Barker wrote:
> Personally, I'd really like to see versioning somehow built into
> python
> itself (and python packages -- eggs solve some of this), then you
> could
> distribute a script that could declare which versions of python a
> script
> was known
Leonardo Santagada wrote:
> And you also make the user know that they are not welcome to install
> python were he wants...
It all depend in who the "user" is, and who the "author" is.
> Try to at least put #!/usr/bin/env python2.5 if all you want is limit
> the python to a specific version,
thanx, ned, conflated u with ed;-)
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
On 29/02/2008, at 01:51, Christopher Barker wrote:
> #!/usr/local/python2.5
>
> or
>
> #!/Library/Frameworks/Python.framework/Versions/2.5/bin/python
>
> I like to do that anyway with production code, as it makes it clear
> which python the script was tested against.
And you also make the user
Ned Deily wrote:
> In your first posting, your script was written using /usr/bin/env:
>
> #! /usr/bin/env python
>
> That leaves you at the mercy of whatever PATH has been set to.
> Suggest you change the cron table entry to explicitly invoke the python
> you want, so (all on one line, of cou
In article <[EMAIL PROTECTED]>,
tom wible <[EMAIL PROTECTED]> wrote:
> i give up: crontab no longer executes python:-P
>
>
> 33 21 * * * /usr/bin/osascript
> /DVR/scripts/noLiveEyeTV.scpt
>
> works fine:
>
> From [EMAIL PROTECTED] Thu Feb 28 21:33:02 2008
> Fro
In article <[EMAIL PROTECTED]>, tom wible <[EMAIL PROTECTED]>
wrote:
> > version (0.18.1) in both Pythons
>
> so why does the python2.5 installer put it in /Lib... & not /System/Lib...
> anyway? will some system scripts fail if i point /system/lib/current to 2.5?
The python installed under /Sy
i give up: crontab no longer executes python:-P
33 21 * * * /usr/bin/osascript
/DVR/scripts/noLiveEyeTV.scpt
works fine:
From [EMAIL PROTECTED] Thu Feb 28 21:33:02 2008
From: [EMAIL PROTECTED] (Cron Daemon)
but
52 21 * * * /DVR/scrip
> version (0.18.1) in both Pythons
so why does the python2.5 installer put it in /Lib... & not /System/Lib...
anyway? will some system scripts fail if i point /system/lib/current to 2.5?
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://ma
On 27 Feb 2008, at 22:49, tom wible wrote:
> just wrote a script to kill live eyetv:
>
> #! /usr/bin/env python
> from appscript import *
> app(u'/Applications/
> EyeTV.app').window[its.name.startswith('EyeTV')].close()
>
> and it works great fom the cli, but not in crontab:
> [...]
> X-Cron-Env
just wrote a script to kill live eyetv:
#! /usr/bin/env python
from appscript import *
app(u'/Applications/EyeTV.app').window[its.name.startswith('EyeTV')].close()
and it works great fom the cli, but not in crontab:
Subject: Cron <[EMAIL PROTECTED]> /DVR/scripts/noLiveEyeTV.py
X-Cron-Env:
X-Cro
13 matches
Mail list logo
