Fix comparison with TZ aware datetime in TimeLimit rule #43
Conversation
This file contains 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
Depending on the string parsed, `parsedate_to_datetime` gives either a timezone aware datetime or a timezone naive datetime. To be able to compare them safely with the current date, this commit makes sure that all datetimes used throughout the application are TZ aware.
|
This PR rebases #32 |
|
Looks good. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Depending on the string parsed,
parsedate_to_datetimegives either atimezone aware datetime or a timezone naive datetime.
To be able to compare them safely with the current date, this commit
makes sure that all datetimes used throughout the application are
TZ aware.