4 ms·
While the API looks really nice and clean, this seems to lack any sort of task distribution mechanism, i.e. tasks run in-process but cannot be passed off to off
by mbi 13y ago
While the API looks really nice and clean, this seems to lack any sort of task distribution mechanism, i.e. tasks run in-process but cannot be passed off to off-process workers, like in e.g. Celery [1] or RQ [2] (the former also does scheduling, the latter is more of a job queueing library, that can do scheduling via an add-on [3])
1: http://www.celeryproject.org/ http://www.celeryproject.org/
2: http://python-rq.org/ http://python-rq.org/
3: https://github.com/ui/rq-scheduler https://github.com/ui/rq-scheduler
- dbader 13y agoI use something like this for submitting jobs to beanstalkc: schedule.every().hour.do(beanstalkc.put, "my_job_id")