Benedikts suggestions

Author: StanFromIreland

Misc/NEWS.d/next/Library/2025-03-08-17-07-00.gh-issue-88473.qg23g8.rst

@@ -1 +1,3 @@
-Implement a fast path for date types in :func:`datetime.date.today`
+Implement a fast path for :class:`datetime.date` objects in :func:`datetime.date.today`
+which results in a 5x performance gain while proper subclasses retain their
+previous performance.

Modules/_datetimemodule.c

@@ -3265,25 +3265,26 @@ date_today(PyObject *cls, PyObject *Py_UNUSED(dummy))
         time_t t;
         time(&t);
 
-        if (_PyTime_localtime(t, &tm) != 0)
+        if (_PyTime_localtime(t, &tm) != 0) {
             return NULL;
+        }
 
         return new_date_ex(tm.tm_year + 1900,
                            tm.tm_mon + 1,
                            tm.tm_mday,
                            (PyTypeObject*)cls);
-    } else {
+    }
+    else {
         PyObject *time;
         PyObject *result;
         time = time_time();
-        if (time == NULL)
+        if (time == NULL) {
             return NULL;
+        }
 
         /* Note well:  today() is a class method, so this may not call
          * date.fromtimestamp.  For example, it may call
-         * datetime.fromtimestamp.  That's why we need all the accuracy
-         * time.time() delivers; if someone were gonzo about optimization,
-         * date.today() could get away with plain C time().
+         * datetime.fromtimestamp.
          */
         result = PyObject_CallMethodOneArg(cls, &_Py_ID(fromtimestamp), time);
         Py_DECREF(time);