[issue20126] sched doesn't handle events added after scheduler starts as expected

Change by Irit Katriel : -- title: sched doesn't handle events added after scheduler starts -> sched doesn't handle events added after scheduler starts as expected ___ Python tracker

[issue20126] sched doesn't handle events added after scheduler starts

Change by Irit Katriel : -- components: +Library (Lib) ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue20126] sched doesn't handle events added after scheduler starts

Irit Katriel added the comment: Reproduced on 3.11. -- nosy: +iritkatriel versions: +Python 3.11 -Python 3.3 ___ Python tracker ___ ___

[issue20126] sched doesn't handle events added after scheduler starts

Ryan Govostes added the comment: This absolutely should be documented. If adding an earlier event is not supported then it should raise an exception. Appearing the enqueue the event but not triggering the callback is especially confusing. It may be obvious behavior to someone who has spent t

[issue20126] sched doesn't handle events added after scheduler starts

Josh Rosenberg added the comment: Why would you not expect this to work in the first place? I'd think a relatively simple use case for schedulers is using a single thread to do the work of a Timer instead of spawning a thread for every Timer. In that sort of use case, the "timer worker" is con

[issue20126] sched doesn't handle events added after scheduler starts

Giampaolo Rodola' added the comment: I don't think this should be documented as personally I wouldn't expect this use case to be working in the first place. -- nosy: +giampaolo.rodola ___ Python tracker __

[issue20126] sched doesn't handle events added after scheduler starts

lo...@blossomhillranch.com added the comment: ok, makes sense. can we put a note in the manual about this limitation? -- ___ Python tracker ___ __

[issue20126] sched doesn't handle events added after scheduler starts

lo...@blossomhillranch.com added the comment: i looks like a different issue. 16165 says you can't add events while the scheduler is running. in my case, i can add them, but they don't run at the correct time. i'll guess at what the problem is... when you start the scheduler, the thread sleep

[issue20126] sched doesn't handle events added after scheduler starts

Serhiy Storchaka added the comment: This is because the scheduler already has executed first event and slept on delaying second event before you have added third event. This is unavoidable for this implementation. sched.scheduler can't be waked when sleep. --

[issue20126] sched doesn't handle events added after scheduler starts

Changes by R. David Murray : -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue20126] sched doesn't handle events added after scheduler starts

R. David Murray added the comment: Search for the issue number in Misc/NEWS. It looks like it was indeed included in 3.3.1. Can you figure out why that fix didn't fix your problem? -- resolution: duplicate -> stage: committed/rejected -> status: closed -> open superseder: sched.sche

[issue20126] sched doesn't handle events added after scheduler starts

lo...@blossomhillranch.com added the comment: i saw that issue before i submitted this one, but it says it was fixed a year ago. i assumed a patch from a year ago would be in 3.3.1. when i see an issue closed with a patch accepted, how do i determine which python version will contain that patc

[issue20126] sched doesn't handle events added after scheduler starts

R. David Murray added the comment: I believe this is a duplicate of issue 16165, which has already been fixed. -- nosy: +r.david.murray resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> sched.scheduler.run() blocks scheduler _

[issue20126] sched doesn't handle events added after scheduler starts

New submission from lo...@blossomhillranch.com: Events added after the scheduler is running, with a delay value before the next event, do not run at the correct time. import sched import time import threading def event( eventNum ): print( 'event', eventNum, time.time() ) s = sched.sch