[flake8-datetimez] Clarify naming guidance for datetime.today (DTZ002) - #26658
Merged
Conversation
ntBre
approved these changes
Jul 9, 2026
ntBre
left a comment
ntBre
left a comment
Contributor
There was a problem hiding this comment.
Thanks! I just moved the new paragraph after the existing ones.
ntBre
changed the title
flake8-datetimez] Clarify naming guidance for datetime.today (DTZ002)
|
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
2 participants
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.
Summary
This updates the DTZ002 documentation to clarify the
datetime.today()naming confusion raised in #23392.datetime.datetime.today()is named like a date helper, but it returns a localdatetime.datetime.now(...)when you need an aware timestamp.Why this changed
The code behavior is already correct; this is a docs-only improvement to make the rule intent easier to understand.
Test Plan
cargo dev generate-docscargo fmt --check --allPATH="$PWD/target/debug:$PATH" uv run --only-group dev --locked python scripts/check_docs_formatted.py