[3.12] gh-106392: Fix inconsistency in deprecation warnings (GH-106436)…

… (#108792) gh-106392: Fix inconsistency in deprecation warnings (GH-106436) They used "datetime" to refer to both the object and the module. (cherry picked from commit d5c5d4b) Co-authored-by: William Andrea <[email protected]>
python · Sep 2, 2023 · b862c25 · b862c25
1 parent 70a378c
commit b862c25
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/Lib/_pydatetime.py b/Lib/_pydatetime.py
@@ -1812,7 +1812,7 @@ def utcfromtimestamp(cls, t):
         warnings.warn("datetime.utcfromtimestamp() is deprecated and scheduled "
                       "for removal in a future version. Use timezone-aware "
                       "objects to represent datetimes in UTC: "
-                      "datetime.fromtimestamp(t, datetime.UTC).",
+                      "datetime.datetime.fromtimestamp(t, datetime.UTC).",
                       DeprecationWarning,
                       stacklevel=2)
         return cls._fromtimestamp(t, True, None)
@@ -1830,7 +1830,7 @@ def utcnow(cls):
         warnings.warn("datetime.utcnow() is deprecated and scheduled for "
                       "removal in a future version. Instead, Use timezone-aware "
                       "objects to represent datetimes in UTC: "
-                      "datetime.now(datetime.UTC).",
+                      "datetime.datetime.now(datetime.UTC).",
                       DeprecationWarning,
                       stacklevel=2)
         t = _time.time()