Eliminate invalid log object errors due to GC changes in Python 3.13.

docs/release-notes.rst

@@ -5,6 +5,7 @@ Release Notes
 .. toctree::
    :maxdepth: 2
 
+   release-notes/version-5.0.2
    release-notes/version-5.0.1
    release-notes/version-5.0.0
 

docs/release-notes/version-5.0.2.rst

@@ -0,0 +1,16 @@
+=============
+Version 5.0.2
+=============
+
+Version 5.0.2 of mod_wsgi can be obtained from:
+
+  https://codeload.github.com/GrahamDumpleton/mod_wsgi/tar.gz/5.0.2
+
+Bugs Fixed
+----------
+
+* Eliminate noise in logs under Python 3.13 when Python garbage collection
+  decides to delay destruction of objects until a second phase, resulting in
+  the `wsgi.errors` log object being accessed after the request had been
+  completed and the log object marked as invalid. This resulted due to changes
+  in garbage collection behaviour in Python 3.13.

src/server/wsgi_logger.c

@@ -176,7 +176,7 @@ static PyObject *Log_flush(LogObject *self, PyObject *args)
     if (thread_info && thread_info->log_buffer)
         return Log_flush((LogObject *)thread_info->log_buffer, args);
 
-    if (self->expired) {
+    if (self->expired && self->s) {
         PyErr_SetString(PyExc_RuntimeError, "log object has expired");
         return NULL;
     }

src/server/wsgi_version.h

@@ -25,8 +25,8 @@
 
 #define MOD_WSGI_MAJORVERSION_NUMBER 5
 #define MOD_WSGI_MINORVERSION_NUMBER 0
-#define MOD_WSGI_MICROVERSION_NUMBER 1
-#define MOD_WSGI_VERSION_STRING "5.0.1"
+#define MOD_WSGI_MICROVERSION_NUMBER 2
+#define MOD_WSGI_VERSION_STRING "5.0.2"
 
 /* ------------------------------------------------------------------------- */