Timezone linter#1444
Open
MaximeBICMTL wants to merge 1 commit into
Open
Conversation
github-actions
Bot
added
Language: Python
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR adds the
DTZlinting rules to our linter configuration, which notably forces Python code to handle timezones when creating a date.Previously, our code did not handle timezones at all, making all datetime objects created with the system timezone.
With this PR, "absolute" datetimes (such as "now") are created and stored in the database with the UTC timezone. User-supplied timezone strings are parsed using a timezone aware-parser (
dateutil) or with no timezone when not available (which uses the system timezone AFAIK).