From 23122af20e6cda535b2f4307e9da2f6ea624db50 Mon Sep 17 00:00:00 2001
From: Mahadev Annabhimoju <219508079+Joosboy@users.noreply.github.com>
Date: Thu, 9 Jul 2026 14:41:40 +0530
Subject: [PATCH 1/2] [ruff] Clarify naming guidance for datetime.today in
 DTZ002 docs

---
 .../src/rules/flake8_datetimez/rules/call_datetime_today.rs   | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/crates/ruff_linter/src/rules/flake8_datetimez/rules/call_datetime_today.rs b/crates/ruff_linter/src/rules/flake8_datetimez/rules/call_datetime_today.rs
index 4545302ba0e3d..4e141810c6012 100644
--- a/crates/ruff_linter/src/rules/flake8_datetimez/rules/call_datetime_today.rs
+++ b/crates/ruff_linter/src/rules/flake8_datetimez/rules/call_datetime_today.rs
@@ -18,6 +18,10 @@ use crate::rules::flake8_datetimez::helpers;
 /// some aspects of reality, which can lead to subtle bugs. Timezone-aware
 /// `datetime` objects are preferred, as they represent a specific moment in
 /// time, unlike "naive" objects.
+
+/// 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.
 ///
 /// `datetime.datetime.today()` creates a "naive" object; instead, use
 /// `datetime.datetime.now(tz=...)` to create a timezone-aware object.

From 8d4a15cbff3d4f79203ebb2afc2d54742243db3c Mon Sep 17 00:00:00 2001
From: Brent Westbrook <36778786+ntBre@users.noreply.github.com>
Date: Thu, 9 Jul 2026 15:52:32 -0400
Subject: [PATCH 2/2] reorder

---
 .../rules/flake8_datetimez/rules/call_datetime_today.rs   | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/crates/ruff_linter/src/rules/flake8_datetimez/rules/call_datetime_today.rs b/crates/ruff_linter/src/rules/flake8_datetimez/rules/call_datetime_today.rs
index 4e141810c6012..061583826b754 100644
--- a/crates/ruff_linter/src/rules/flake8_datetimez/rules/call_datetime_today.rs
+++ b/crates/ruff_linter/src/rules/flake8_datetimez/rules/call_datetime_today.rs
@@ -18,14 +18,14 @@ use crate::rules::flake8_datetimez::helpers;
 /// some aspects of reality, which can lead to subtle bugs. Timezone-aware
 /// `datetime` objects are preferred, as they represent a specific moment in
 /// time, unlike "naive" objects.
-
-/// 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.
 ///
 /// `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