Update match name removal language to be definitive

- Change "25 years" to "30 years" to reflect actual time - Replace speculative "this decade, if ever" / "7 years" language with clear statement that we will never remove the original match name Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
python · gpshead · Feb 16, 2026 · Feb 5, 2022 · Jan 30, 2023 · Jan 30, 2023
commit 58d8f579c97918f142bfa4b0bd6fbd4c336c41b8
diff --git a/Doc/library/re.rst b/Doc/library/re.rst
@@ -1788,8 +1788,8 @@ understand the intended semantics. When reading :func:`~re.match` there remains
 a seed of doubt about the intended behavior to anyone not already familiar with
 this old Python gotcha.
 
-We **do not** plan to deprecate and remove the older *match* name in this
-decade, if ever, as it has been used in code for over 25 years.
+We will **never** remove the original :func:`~re.match` name, as it has been
+used in code for over 30 years.
 
 .. versionadded:: next
 

diff --git a/Misc/NEWS.d/next/Library/2022-02-05-00-15-03.bpo-42353.0ebVGG.rst b/Misc/NEWS.d/next/Library/2022-02-05-00-15-03.bpo-42353.0ebVGG.rst
@@ -7,5 +7,4 @@ the term "match" to mean what Python uses the term "search" for. The
 unadorened "match" name in Python has been a frequent case of confusion and
 coding bugs due to the inconsistency with the rest if the software industry.
 
-No plans to remove and deprecate the existing ``match`` names exist. If that
-were to happen it would be at minimum 7 years in the future.
+We will never remove the original ``match`` name.