René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Timer + long-running callback expectations","articleBody":"Do we want to say anything about how we expect our event timers to behave with regard to when they fire? Should a timer be ticking continuously and firing when requested regardless of other tasks occurring (maybe in a separate thread), or should the timers fire at (time in callback + interval)?\r\n\r\nFollowing up with some results about what the various backends currently do for callbacks that last longer than the timers with the following test script that will either print ~1/second or every 2-seconds.\r\n\r\n```python\r\nimport time\r\nimport matplotlib.pyplot as plt\r\n\r\nfig = plt.figure()\r\n\r\ndef on_timer():\r\n    print(time.ctime())\r\n    time.sleep(1)\r\n\r\ntimer = fig.canvas.new_timer(interval=1000)\r\ntimer.add_callback(on_timer)\r\ntimer.start()\r\nfig.canvas.start_event_loop(10)\r\n```\r\n\r\n**macos:** 2-seconds\r\n**tkagg:** 2-seconds\r\n**qtagg:** 1-second\r\n**gtk4agg:** 1-second\r\n**wxagg:** 2-seconds\r\n\r\nSo I can't say we have a standard right now, or if we should even try to set an expectation of one or the other cases to make things consistent.\r\n\r\n_Originally posted by @greglucas in https://github.com/matplotlib/matplotlib/pull/29023#discussion_r1817600768_\r\n            ","author":{"url":"https://github.com/greglucas","@type":"Person","name":"greglucas"},"datePublished":"2024-10-28T17:08:06.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":10},"url":"https://github.com/29029/matplotlib/issues/29029"}