Docs docs docs docs docs

Author: gpshead

Doc/backup.db

@@ -0,0 +1,2 @@
+BEGIN TRANSACTION;
+COMMIT;

Doc/dump.sql

@@ -500,6 +500,11 @@ Some details you should read once, but won't need to remember:
   everything following the leftmost colon and any module information in the
   exception name is ignored.
 
+* When the :const:`IGNORE_EXCEPTION_TIMESTAMPS` doctest option is specified,
+  timestamps of the formats that :envvar:`PYTHON_TRACEBACK_TIMESTAMPS`
+  environment variable could append to exception messages are stripped from
+  tracebacks generated by the code under test before comparison.
+
 * The interactive shell omits the traceback header line for some
   :exc:`SyntaxError`\ s.  But doctest uses the traceback header line to
   distinguish exceptions from non-exceptions.  So in the rare case where you need
@@ -625,6 +630,22 @@ doctest decides whether actual output matches an example's expected output:
       to the module containing the exception under test.
 
 
+.. data:: IGNORE_EXCEPTION_TIMESTAMPS
+
+   When the :envvar:`PYTHON_TRACEBACK_TIMESTAMPS` environment variable is set,
+   exception and warning messages rendered in tracebacks may have a timestamp
+   value appended after the message.  This strips all possible formats of that
+   `` <@2025-02-08T01:21:28.675309>`` timestamp tag that may be appended to an
+   exception message in generated tracebacks before comparing.
+
+   :const:`ELLIPSIS` and :const:`IGNORE_EXCEPTION_DETAIL` could also be used to
+   avoid matching those.  This can be cleaner when you need to test specific
+   details of exception messages.
+
+   .. versionadded:: next
+      :const:`IGNORE_EXCEPTION_TIMESTAMPS` was added.
+
+
 .. data:: SKIP
 
    When specified, do not run the example at all.  This can be useful in contexts