Use timezone-aware datetimes -- ruff check --select=DTZ #84
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.
https://docs.astral.sh/ruff/rules/#flake8-datetimez-dtz
%
ruff check --select=DTZ --statistics
%
ruff rule DTZ001
call-datetime-without-tzinfo (DTZ001)
Derived from the flake8-datetimez linter.
What it does
Checks for
datetime
instantiations that lack atzinfo
argument.Why is this bad?
datetime
objects are "naive" by default, in that they do not includetimezone information. "Naive" objects are easy to understand, but ignore
some aspects of reality, which can lead to subtle bugs. Timezone-aware
datetime
objects are preferred, as they represent a specific moment intime, unlike "naive" objects.
By providing a
tzinfo
value, adatetime
can be made timezone-aware.Example
Use instead:
Or, for Python 3.11 and later: