Clean up nits

pganssle · pganssle · commit 9542f545e08f · 2022-05-03T14:02:05.000-06:00
1. Add UTC definition into C implementation as well (just for
   consistency, there's no particular reason not to simply assign the
   alias in the Python code later).

2. Move `..versionadded` tag into the right place
diff --git a/Doc/library/datetime.rst b/Doc/library/datetime.rst
@@ -84,11 +84,12 @@ The :mod:`datetime` module exports the following constants:
    The largest year number allowed in a :class:`date` or :class:`.datetime` object.
    :const:`MAXYEAR` is ``9999``.
 
-.. versionadded:: 3.11
 .. attribute:: UTC
 
    Alias for the UTC timezone singleton :attr:`datetime.timezone.utc`.
 
+   .. versionadded:: 3.11
+
 Available Types
 ---------------
 
diff --git a/Lib/datetime.py b/Lib/datetime.py
@@ -2290,7 +2290,7 @@ def _name_from_offset(delta):
             return f'UTC{sign}{hours:02d}:{minutes:02d}:{seconds:02d}'
         return f'UTC{sign}{hours:02d}:{minutes:02d}'
 
-timezone.utc = timezone._create(timedelta(0))
+UTC = timezone.utc = timezone._create(timedelta(0))
 
 # bpo-37642: These attributes are rounded to the nearest minute for backwards
 # compatibility, even though the constructor will accept a wider range of
@@ -2515,5 +2515,3 @@ def _name_from_offset(delta):
     # appropriate to maintain a single module level docstring and
     # remove the following line.
     from _datetime import __doc__
-
-UTC = timezone.utc
diff --git a/Modules/_datetimemodule.c b/Modules/_datetimemodule.c
@@ -6634,6 +6634,10 @@ _datetime_exec(PyObject *module)
         return -1;
     }
 
+    if (PyModule_AddObjectRef(module, "UTC", PyDateTime_TimeZone_UTC) < 0) {
+        return -1;
+    }
+
     /* A 4-year cycle has an extra leap day over what we'd get from
      * pasting together 4 single years.
      */
