Jason Tackaberry wrote:
> On 2007-10-25 15:55, Dirk Meyer wrote:
>> First draft is in SVN, feel free to improve
>
> Why have it as a separate file? Seems to belong nicely in timer.py
Fixed. AtTimer and OneShotAtTimer work now.
Dischi
--
"To know recursion, you must first know recursion"
pgp
On 2007-10-25 15:55, Dirk Meyer wrote:
> First draft is in SVN, feel free to improve
Why have it as a separate file? Seems to belong nicely in timer.py
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through
Dirk Meyer wrote:
> Jason Tackaberry wrote:
>> On 2007-10-25 08:55, Hans Meine wrote:
>>> I also prefer kwargs. However, I wondered about your double (()), and
>>> I agree
>>> with Jason that a single timer per object simplifies things.
>>
>> I dislike the differentiation between, as in Duncan's ex
On 2007-10-25 15:31, Hans Meine wrote:
> I only read about Timer, and did not try it out - what happens if the
> callback
> returns None?
None is safe. It checks for False specifically. So you have to go out
of your way to cause the timer to be unregistered. Clearly needing to
explicitly return
On Donnerstag 25 Oktober 2007, Dirk Meyer wrote:
> | class AtTimer(Callback)
> | def schedule(hour=range(24), min=range(60), sec=0):
> | ...
> | def stop()
> | ...
>
> Callback return False and it will be removed, just like Timer.
I only read about Timer, and did not try it
Jason Tackaberry wrote:
> On 2007-10-25 08:55, Hans Meine wrote:
>> I also prefer kwargs. However, I wondered about your double (()), and
>> I agree
>> with Jason that a single timer per object simplifies things.
>
> I dislike the differentiation between, as in Duncan's example, min and
> mins kwar
On Donnerstag 25 Oktober 2007, Jason Tackaberry wrote:
> The idea was mins allows an interval, whereas min was a fixed time. An
> interval is just a shorthand way of specifying a list of possible values
> for min. So how about we just let the kwargs accept sequences or range
> objects.
>
> t.sc
Jason Tackaberry wrote:
> On 2007-10-25 08:55, Hans Meine wrote:
>> I also prefer kwargs. However, I wondered about your double (()), and
I wonder too, wanted to make it a tuple, so a single argument, forgot
about the kwargs when I wrote it.
>> I agree
>> with Jason that a single timer per object
On 2007-10-25 09:56, Jason Tackaberry wrote:
> t.schedule(min = range(0, 60, 50)) # every 5 minutes
That should be range(0, 60, 5) of course.
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to
On 2007-10-25 08:55, Hans Meine wrote:
> I also prefer kwargs. However, I wondered about your double (()), and
> I agree
> with Jason that a single timer per object simplifies things.
I dislike the differentiation between, as in Duncan's example, min and
mins kwarg. I'm never going to remember wh
Am Donnerstag, 25. Oktober 2007 07:17:18 schrieb Duncan Webb:
> Not being a sys admin, I must look up the cron command syntax every time :)
Yeah, and if some fields are optional, it becomes really ambiguous ("In the
face of ambiguity, refuse the temptation to guess.").
> May be the name CronTime
> On 2007-10-23 15:21, Dirk Meyer wrote:
>> As for the API I'm thinking of at/schedule, remove and list.
>>
>> | t = CronTimer(callback)
>> | t.at("*:15")
>> | t.at("*:20")
>> | t.list() => [ "*:15", "*:20" ]
>
> Is it necessary to support multiple times per CronTimer object? I think
> this just c
On 2007-10-23 15:21, Dirk Meyer wrote:
> As for the API I'm thinking of at/schedule, remove and list.
>
> | t = CronTimer(callback)
> | t.at("*:15")
> | t.at("*:20")
> | t.list() => [ "*:15", "*:20" ]
Is it necessary to support multiple times per CronTimer object? I think
this just complicates th
Dirk Meyer wrote:
> Duncan Webb wrote:
>> OT: A big assumption that broadcasters transmit on time, there is nearly
>> always a couple of minutes betweens shows, but when they do then 15 secs
>> lead-in is better than missing the beginning.
>>
>> You don't have to follow my syntax could do it like:
Duncan Webb wrote:
> OT: A big assumption that broadcasters transmit on time, there is nearly
> always a couple of minutes betweens shows, but when they do then 15 secs
> lead-in is better than missing the beginning.
>
> You don't have to follow my syntax could do it like:
> | t = CronTimer(callbac
Dirk Meyer wrote:
> Jason Tackaberry wrote:
>> On 2007-10-23 07:34, Duncan Webb wrote:
>>> Does kaa.notifier.Timer have an 'at' function so that something can be
>>> run at a specific interval? The recordserver runs its loop at the top of
>>> the minute so a function like Timer(handler).at('*:00')
Jason Tackaberry wrote:
> On 2007-10-23 07:34, Duncan Webb wrote:
>> Does kaa.notifier.Timer have an 'at' function so that something can be
>> run at a specific interval? The recordserver runs its loop at the top of
>> the minute so a function like Timer(handler).at('*:00') would be very
>> useful.
Jason Tackaberry wrote:
> On 2007-10-23 01:46, Duncan Webb wrote:
>> I have a little bit of a problem with the recordserver not getting
>> events from it's plug-ins. The problem is that kaa.notifier.loop() and
>> app.run() don't return so I can't have both in a program, can I?
>
> Ideally app.run(
On 2007-10-23 07:34, Duncan Webb wrote:
> Does kaa.notifier.Timer have an 'at' function so that something can be
> run at a specific interval? The recordserver runs its loop at the top of
> the minute so a function like Timer(handler).at('*:00') would be very
> useful. This could be extended to run
On 2007-10-23 01:46, Duncan Webb wrote:
> I have a little bit of a problem with the recordserver not getting
> events from it's plug-ins. The problem is that kaa.notifier.loop() and
> app.run() don't return so I can't have both in a program, can I?
Ideally app.run() just calls something like app.s
Duncan Webb wrote:
> Duncan Webb wrote:
>> Dirk Meyer wrote:
>>> Duncan Webb wrote:
>
The recordserver doesn't work.
>>> What does not work? Well, yes, the recordserver uses the twisted
>>> mainloop and Freevo uses kaa.notifier. That sounds like a problem. But
>>> don't you want to get rid of
Duncan Webb wrote:
> Dirk Meyer wrote:
>> Duncan Webb wrote:
>>> The recordserver doesn't work.
>>
>> What does not work? Well, yes, the recordserver uses the twisted
>> mainloop and Freevo uses kaa.notifier. That sounds like a problem. But
>> don't you want to get rid of twisted anyway?
>
> I fo
Duncan Webb wrote:
> Dirk Meyer wrote:
>> Duncan Webb wrote:
>>> This mostly works, at least I haven't found any plug-ins that are
>>> broken.
>>
>> It is kind of ugly because the stuff still uses the old poll code. In
>> the future plugisn should register the timer to kaa.notifier.
>
> I this al
Dirk Meyer wrote:
> Duncan Webb wrote:
>> This mostly works, at least I haven't found any plug-ins that are
>> broken.
>
> It is kind of ugly because the stuff still uses the old poll code. In
> the future plugisn should register the timer to kaa.notifier.
I this all, just replace poll for timer
Duncan Webb wrote:
> This mostly works, at least I haven't found any plug-ins that are
> broken.
It is kind of ugly because the stuff still uses the old poll code. In
the future plugisn should register the timer to kaa.notifier.
> The recordserver doesn't work.
What does not work? Well, yes, th
Dirk Meyer wrote:
> Duncan Webb wrote:
>> Dirk Meyer wrote:
>>> Duncan Webb wrote:
Dirk Meyer wrote:
> Jason Tackaberry wrote:
>> On Sun, 2007-08-26 at 07:59 -0700, Michael Beal wrote:
>>> Wouldn't it make sense to use SQLite for this instead? The record
>>> schedule is curren
26 matches
Mail list logo
