[issue37174] sched.py: run() is caught in delayfunc even if all events are cancelled.

2019-06-07 Thread Raymond Hettinger
Raymond Hettinger added the comment: Marking this as 3.9 because it is an API change. Also, you can already control the delayfunc through the current API, so I don't see the necessity of a changing the default which seems to work fine for most users. Tim, what do you think? --

[issue37174] sched.py: run() is caught in delayfunc even if all events are cancelled.

2019-06-07 Thread Terry J. Reedy
Terry J. Reedy added the comment: 3.6 only gets security fixes. 3.7, 3.8 only get bugfixes. Something new should be a separate PR. -- nosy: +terry.reedy stage: -> test needed versions: -Python 3.6 ___ Python tracker

[issue37174] sched.py: run() is caught in delayfunc even if all events are cancelled.

2019-06-06 Thread Maximilian Ernestus
New submission from Maximilian Ernestus : When I remove all events from a scheduler while its run() is being executed (with blocking=True in another thread), run() continues to block for some time because it is caught in its delayfunc which is time.sleep by default. This issue can easily be