31–40 of 55 posts
Earlier quoted context omitted.
If it took less than 5 minutes to boot then I can't see why it wouldn't work. How would that work for other schedulers? Also, if a server reboots that's quite bad all round anyway. Hopefully you'd be notified directly.
Other schedulers have a durable database of attempted runs. This doesn't seem to have anything like that.
If you're going to build a framework like this, please please put your consistency behavior and retry behavior at the top of your docs.
Yes, 100% this. Too many frameworks claim that they are "easy" just to find out they left out things that other older frameworks have already solved. While we are on this: Do you know of any task scheduler framework that is similar to celery, but has better guarantees around task execution than what acks_late= True gives you? I always find myself building a system that stores the really important Tasks in Postgres so…
I'm using APScheduler for most of my scheduling tasks. Does Red Engine integrate with asyncio? When searching the docs for this keyword no hits showed up.
https://github.com/temporalio/sdk-python
Disclaimer: I work for Temporal
Not to be confused with REDengine by CD Projekt Red, used to make the Witcher and Cyberpunk 2077 games [0]. They're moving to Unreal Engine 5 though. [0] https://witcher.fandom.com/wiki/REDengine
Not to be confused with REDengine by CD Projekt Red, used to make the Witcher and Cyberpunk 2077 games [0]. They're moving to Unreal Engine 5 though. [0] https://witcher.fandom.com/wiki/REDengine
Yeah, when I read the title I was like: "wtf, CDPR released Python version of their engine?"
Unfortunately CDPR's latest RED Engine 4 will not be released as open source in the forseeable future, it's basically dead and locked away, and will probably never see the light of day. Maybe it would be open sourced but in something like 20 years time.
This fits my use case so perfectly! I have a very small internal app taking care of organizing seminar talks, calendars, email announcements, recordings of the talks, and signups. It is a single python file of less than 1500 lines and an sqlite database. This library is so perfect for taking care of scheduled events. Everything else I have found is ridiculously over-complicated of a solution.
How does it handle state and restarts? What happens if a job is scheduled to run "before 10am", then the entire server restarts at 9:55am, will it try to run that same job again when it boots back up?
If it took less than 5 minutes to boot then I can't see why it wouldn't work. How would that work for other schedulers? Also, if a server reboots that's quite bad all round anyway. Hopefully you'd be notified directly.
from redengine import RedEngine
app = RedEngine()
@app.task('daily')
def do_things():
...
if __name__ == "__main__":
app.run()
Might wanna fix that.
Earlier quoted context omitted.
Other schedulers have a durable database of attempted runs. This doesn't seem to have anything like that.
Would you have a recommendation for an easy to use Python scheduler with such a feature for a personal project?