jobqueue: add support for specifying next_t in datetime.datetime or datetime.time#482
Closed
jobqueue: add support for specifying next_t in datetime.datetime or datetime.time#482
Conversation
Member
Author
|
Related to #452 |
Member
Author
|
closing in favour of #484 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Title says it all, I guess. Many people asked for it, so here we go. You can now specify the
next_tparameter ofJobQueue.putasdatetime.datetimeordatetime.time, so the job will run at exactly the specified (date and) time.If you pass a
datetime.timeobject fornext_tand it's already later than the specified time (eg it's 10:00 andnext_tistime(8, 30)), the job will execute the next day.I made the
intervalparameter forJoboptional, so you can just leave it for non-repeating jobs (however, you must explicitly passrepeat=False)