Change to Python 3.18

Author: StanFromIreland

Doc/deprecations/pending-removal-in-3.18.rst

@@ -1,6 +1,11 @@
 Pending removal in Python 3.18
 ------------------------------
 
+* :mod:`datetime`:
+
+  * :meth:`~datetime.datetime.strptime` calls using a format string containing
+    a day of month without a year. This has been deprecated since Python 3.13.
+
 * :mod:`decimal`:
 
   * The non-standard and undocumented :class:`~decimal.Decimal` format

Doc/library/datetime.rst

@@ -1168,7 +1168,7 @@ Other constructors, all class methods:
       :exc:`DeprecationWarning` is now emitted.  This is to avoid a quadrennial
       leap year bug in code seeking to parse only a month and day as the
       default year used in absence of one in the format is not a leap year.
-      Such *format* values may raise an error as of Python 3.15.  The
+      Such *format* values may raise an error as of Python 3.18.  The
       workaround is to always include a year in your *format*.  If parsing
       *date_string* values that do not have a year, explicitly add a year that
       is a leap year before parsing:
@@ -2532,7 +2532,7 @@ requires, and these work on all supported platforms.
 |           | zero-padded decimal number.    |                        |       |
 +-----------+--------------------------------+------------------------+-------+
 |  ``%d``   | Day of the month as a          | 01, 02, ..., 31        | \(9), |
-|           | zero-padded decimal number.    |                        | \(10  |
+|           | zero-padded decimal number.    |                        | \(10) |
 +-----------+--------------------------------+------------------------+-------+
 |  ``%D``   | Equivalent to ``%m/%d/%y``.    | 11/10/2025             | \(9), |
 |           |                                |                        | \(0)  |
@@ -2868,11 +2868,11 @@ Notes:
       >>> datetime.strptime(f"{month_day};1984", "%m/%d;%Y")  # No leap year bug.
       datetime.datetime(1984, 2, 29, 0, 0)
 
-   .. deprecated-removed:: 3.13 3.15
+   .. deprecated-removed:: 3.13 3.18
       :meth:`~.datetime.strptime` calls using a format string containing
       a day of month without a year now emit a
-      :exc:`DeprecationWarning`. In 3.15 or later we may change this into
-      an error or change the default year to a leap year. See :gh:`70647`.
+      :exc:`DeprecationWarning`. In 3.18 we will change this into
+      an error or change the default year to a leap year.
 
 .. rubric:: Footnotes
 

Lib/_strptime.py

@@ -475,10 +475,9 @@ def repl(m):
             import warnings
             warnings.warn("""\
 Parsing dates involving a day of month without a year specified is ambiguous
-and fails to parse leap day. The default behavior will change in a future Python
-version to either always raise an exception or to use a different default year.
-To avoid trouble, add a specific year to the input & format.
-See https://github.com/python/cpython/issues/70647.""",
+and fails to parse leap day. The default behavior will change in Python 3.18
+to either always raise an exception or to use a different default year.
+To avoid trouble, add a specific year to the input and format.""",
                           DeprecationWarning,
                           skip_file_prefixes=(os.path.dirname(__file__),))
         return format

Misc/NEWS.d/next/Library/2026-02-07-12-54-20.gh-issue-70647.Bja_Lk.rst

@@ -0,0 +1,2 @@
+Include the ``%e`` format code in the :meth:`~datetime.datetime.strptime`
+deprecation for day-of-month format codes used without a year.