Open asdf8dfafjk opened 1 year ago
The IScheduler
interface and the tempora
library the implementation is based on are not designed for an async application. They assume an architecture where the application is repeatedly polling to check whether one of the scheduled jobs should run with .run_pending()
. In an async application, a timer should be scheduled with the event loop (or a higher-level interface like asyncio.sleep
in a task); the event loop automatically dispatches the job at the right time without polling.
@rht Should I still test? (I sense user: andersk's comment implies it would be futile)
Hello, I'm using this package via github.com/zulip/zulip 's irc<->zulip bridge, and am coming across the following error. The zulip integration uses the async reactor but @rht 's research says https://github.com/jaraco/irc/blob/4c15d340105644c127b4a849774e232070a5bfcd/irc/bot.py#L107 incorrectly assumes a sync reactor and that the scheduler attribute referred to in the said code doesn't exist for the async reactor.
Could you suggest a fix here?
Full error message: