-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passing "schedule" as a keyword argument to delay() #102
Comments
delay
After spelunking a bit, I see that if a task is scheduled it is considered as I'm guessing that (as much as I hate to say it) tasktiger is potentially not a good fit for my current efforts, and I will need to use something more robust (and gross) like celery to get the job done. If this is not the case, please point me in the right direction, as I would rather issue a PR to tasktiger then use celery. |
Can you clarify on what |
I think I see what you want. The way |
+1 this is a feature I would use too. As an example, rq-scheduler (https://github.com/rq/rq-scheduler) allows dynamic creation of periodic/scheduled tasks for python-rq from version 0.3 onwards. The scheduler runs as a separate process that polls redis every minute for new scheduled tasks, and adds them onto the relevant queues. |
Hey team! First of all great work on tasktiger, it rocks.
I have a need to be able to dynamically create tasks with different user defined schedules. As such, I cannot provide a schedule when decorating the task function, and instead need to do it when I call
delay
on the task. I see in the docs thatschedule
is not a supported keyword argument, and was thinking about working on a pull request to add support for this, but I assumed that this was an intentional design decision for some reason. Could you provide more information about why this is not available as a kwarg for thedelay
call?Thanks!
The text was updated successfully, but these errors were encountered: