This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients akuchling, djarb, facundobatista, forest, giampaolo.rodola, gvanrossum, intgr, j1m, jafo, josiahcarlson, kevinwatters, markb, mcdonc, pitrou, r.david.murray, stutzbach, tseaver
Date 2010-05-11.17:08:52
SpamBayes Score 0.05977034
Marked as misclassified No
Message-id <1273597428.3315.18.camel@localhost.localdomain>
In-reply-to <1273596935.73.0.967941041182.issue1641@psf.upfronthosting.co.za>
Content
> Adding a call:
> 
> scheduler = sched.scheduler(time.time, time.sleep)
> scheduler.enter(10, 1, function, (arg,))
> 
> ...vs:
> 
> asyncore.call_later(10, function, arg)

I don't really see the difference. How hard it is to build a scheduler
object at startup and store it somewhere in your globals or on one of
your objects?

The main improvement I could see would be to make the arguments to
sched.scheduler() optional, and default to time.time and time.sleep.
History
Date User Action Args
2010-05-11 17:08:56pitrousetrecipients: + pitrou, gvanrossum, akuchling, facundobatista, jafo, josiahcarlson, tseaver, forest, giampaolo.rodola, kevinwatters, djarb, stutzbach, markb, r.david.murray, intgr, mcdonc, j1m
2010-05-11 17:08:52pitroulinkissue1641 messages
2010-05-11 17:08:52pitroucreate