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 stutzbach
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:56:25
SpamBayes Score 0.00021834002
Marked as misclassified No
Message-id <AANLkTilOLf0_nVMxX6r2e3Mm-rSa7eEV0fIzBhJSHOay@mail.gmail.com>
In-reply-to <1273596935.73.0.967941041182.issue1641@psf.upfronthosting.co.za>
Content
On Tue, May 11, 2010 at 11:55 AM, Giampaolo Rodola'
<report@bugs.python.org> wrote:
> Moreover, reset() and delay() methods are not implemented in sched.
>
> Other problems which comes to mind are: you can't easily know whether a call has already been cancelled, you can't manually fire it before the timeout has expired and I'm not even sure whether it's possible to pass kwargs to enter(), which is crucial (with call_later you can do it like this: asyncore.call_later(10, function, x, y, z='foo')).

These are nice features, but wouldn't it make more sense to add them to sched?

That would provide them to other users of sched, while keeping the
asyncore code simpler.
History
Date User Action Args
2010-05-11 17:56:27stutzbachsetrecipients: + stutzbach, gvanrossum, akuchling, facundobatista, jafo, josiahcarlson, tseaver, pitrou, forest, giampaolo.rodola, kevinwatters, djarb, markb, r.david.murray, intgr, mcdonc, j1m
2010-05-11 17:56:25stutzbachlinkissue1641 messages
2010-05-11 17:56:25stutzbachcreate