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 neologix
Recipients bquinlan, gvanrossum, neologix, pitrou, r.david.murray, serhiy.storchaka
Date 2013-05-13.15:24:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
> To be honest I can't find much to say about this proposal,

Hum, OK, I thought it would be a useful addition :-)

> but I think it would be good if the time function were configurable (both for test purposes, and to allow passing e.g. time.monotonic). I suppose this could be an executor option.

Note that the time function must be "real" time, since the sleep are
based on condition.wait() (otherwise if you just call an arbitrary
sleep() function you can't be woken up when a new task with an earlier
deadline is submitted).
So it's different from the sched module, we can't really support
arbitrary time functions.

Note that I do think it would be a good idea to use time.monotonic()
when available (almost all modules have been updated, except the
future one). That's probably another issue, though.
Date User Action Args
2013-05-13 15:24:50neologixsetrecipients: + neologix, gvanrossum, bquinlan, pitrou, r.david.murray, serhiy.storchaka
2013-05-13 15:24:50neologixlinkissue17956 messages
2013-05-13 15:24:50neologixcreate