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

Changes by Giampaolo Rodola' : -- nosy: +josiah.carlson, josiahcarlson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

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

Changes by Giampaolo Rodola' : -- assignee: -> giampaolo.rodola resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ ___

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

Roundup Robot added the comment: New changeset 2975618965c0 by Giampaolo Rodola' in branch 'default': Fix #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 -- nosy: +pyt

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

Giampaolo Rodola' added the comment: "blocking" seems the most explicit to me. With this, we can also fix issue1641 by providing a specific section into asyncore doc which explains how to use asyncore in conjunction with sched. -- ___ Python tracker

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

Antoine Pitrou added the comment: That's a good point. Then perhaps call the flag "wait" or "blocking", since it avoids false positives and is more explicit than "async"? -- ___ Python tracker ___

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

Giampaolo Rodola' added the comment: 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 remem

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

Changes by Ezio Melotti : -- components: +Library (Lib) stage: -> patch review type: -> feature request ___ Python tracker ___ ___ P

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

Antoine Pitrou added the comment: I think this would be better served by a separate method. You could call it e.g. run_nowait(). -- nosy: +pitrou ___ Python tracker ___ ___

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

Changes by Giampaolo Rodola' : -- keywords: +patch Added file: http://bugs.python.org/file23746/sched-async.patch ___ Python tracker ___ _

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

New submission from Giampaolo Rodola' : 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. -- messages: 148095 nosy: giampaolo.rodola priority: normal severity: normal status: o