sched - provide an "async" argument for run() method

[giampaolo]

BPO	13449
Nosy	@josiahcarlson, @pitrou, @giampaolo
Files	sched-async.patch

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/giampaolo'
closed_at = <Date 2011-12-14.13:41:06.308>
created_at = <Date 2011-11-22.00:19:43.202>
labels = ['type-feature', 'library']
title = 'sched - provide an "async" argument for run() method'
updated_at = <Date 2011-12-14.13:41:46.257>
user = 'https://github.com/giampaolo'

bugs.python.org fields:

activity = <Date 2011-12-14.13:41:46.257>
actor = 'giampaolo.rodola'
assignee = 'giampaolo.rodola'
closed = True
closed_date = <Date 2011-12-14.13:41:06.308>
closer = 'giampaolo.rodola'
components = ['Library (Lib)']
creation = <Date 2011-11-22.00:19:43.202>
creator = 'giampaolo.rodola'
dependencies = []
files = ['23746']
hgrepos = []
issue_num = 13449
keywords = ['patch']
message_count = 6.0
messages = ['148095', '148097', '149443', '149444', '149445', '149448']
nosy_count = 5.0
nosy_names = ['josiahcarlson', 'pitrou', 'giampaolo.rodola', 'josiah.carlson', 'python-dev']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue13449'
versions = ['Python 3.3']

[giampaolo]

If True it would run the scheduled functions due to expire soonest (if any) and then return.
This would make sched module usable into asynchronous applications.

[pitrou]

I think this would be better served by a separate method. You could call it e.g. run_nowait().

[giampaolo]

What about run(nowait=...) or run(only_ready=...)?
Doing this as a separate method seems unnecessarily complicated to me in terms of implementation (move run logic into _run, add "run" and "run_nowait", etc...).
Most importantly, the user will have to remember two methods which are basically equivalent in terms of "what they actually do".

[pitrou]

That's a good point. Then perhaps call the flag "wait" or "blocking", since it avoids false positives and is more explicit than "async"?

[giampaolo]

"blocking" seems the most explicit to me.
With this, we can also fix bpo-1641 by providing a specific section into asyncore doc which explains how to use asyncore in conjunction with sched.

[python-dev]

New changeset 2975618965c0 by Giampaolo Rodola' in branch 'default':
Fix bpo-13449: add 'blocking' parameter to sched.scheduler.run() so that the scheduler can be used in non-blocking applications
http://hg.python.org/cpython/rev/2975618965c0