Skip to content

[flake8-datetimez] Clarify naming guidance for datetime.today (DTZ002) #26658

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ntBre merged 2 commits into from
Jul 9, 2026
Merged

[flake8-datetimez] Clarify naming guidance for datetime.today (DTZ002) #26658

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
23122af
[ruff] Clarify naming guidance for datetime.today in DTZ002 docs
Joosboy Jul 9, 2026
8d4a15c
reorder
ntBre Jul 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions crates/ruff_linter/src/rules/flake8_datetimez/rules/call_datetime_today.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,10 @@ use crate::rules::flake8_datetimez::helpers;
/// `datetime.datetime.today()` creates a "naive" object; instead, use
/// `datetime.datetime.now(tz=...)` to create a timezone-aware object.
///
/// The name `today()` can be misleading, because it suggests a calendar date,
/// but it actually returns the current local date and time as a `datetime`.
/// That can make intent harder to infer when reading code.
///
/// ## Example
/// ```python
/// import datetime
Expand Down
Loading