Skip to content

gh-86519: Add prefixmatch APIs to the re module #31137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gpshead merged 19 commits into from
Feb 16, 2026
Merged

gh-86519: Add prefixmatch APIs to the re module #31137

Changes from 1 commit
Commits
Show all changes
19 commits
Select commit Hold shift + click to select a range
587dc4d
bpo-42353: Add prefixmatch APIs to the re module.
gpshead Feb 5, 2022
c7d1581
Merge branch 'main' into prefixmatch-b42353
gpshead Jan 30, 2023
fa2885e
fix editor fat finger typo during the merge. #vim
gpshead Jan 30, 2023
6195ad7
3.12
gpshead Jan 30, 2023
0296f29
Merge branch 'main' into prefixmatch-b42353
hauntsaninja Feb 26, 2023
bab8e8b
Merge main and modernize the relevant docs.
gpshead Apr 18, 2025
149f6e4
Simplify, don't have duplicate definitions.
gpshead Apr 19, 2025
e176692
Merge main into prefixmatch-b42353
gpshead Jan 31, 2026
58d8f57
Update match name removal language to be definitive
gpshead Jan 31, 2026
3cd9d71
Fix re.rst examples after match to search conversion
gpshead Jan 31, 2026
d6090bb
Replace name-parsing examples with Monty Python references
gpshead Feb 1, 2026
341972f
Address reviewer docs feedback: prefer prefixmatch throughout
gpshead Feb 9, 2026
cd8d85d
Statically alias match to prefixmatch instead of runtime memcpy
gpshead Feb 9, 2026
74d51b3
Merge main into prefixmatch-b42353
gpshead Feb 9, 2026
4abdff0
Fix whatsnew 3.15 RST heading that matches git conflict marker
gpshead Feb 9, 2026
6bacfb0
docs, remove errant "if ever"
gpshead Feb 9, 2026
40e6a2a
doc wording tweaks jf clarity
gpshead Feb 9, 2026
b3c6948
Extract do_test_match_getitem helper to preserve git blame
gpshead Feb 9, 2026
b277981
tweak news to match docs
gpshead Feb 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
doc wording tweaks jf clarity
  • Loading branch information
@gpshead
gpshead committed Feb 9, 2026
commit 40e6a2acef765057953c5472d20b2eac88c3209e
25 changes: 13 additions & 12 deletions Doc/library/re.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -958,12 +958,12 @@ Functions
older Python versions.

.. versionchanged:: next
An alternate :func:`~re.prefixmatch` name with this API was added as a
more descriptive explicit name for the behavior of :func:`~re.match`. Use
it to more clearly express intent. The norm in other languages and
regular expression implementations is to use the term *match* to refer to
the behavior of what Python has always called :func:`~re.search`. See
:ref:`prefixmatch-vs-match`.
The alternate :func:`~re.prefixmatch` name of this API was added as a
more explicitly descriptive name than :func:`~re.match`. Use it to better
express intent. The norm in other languages and regular expression
implementations is to use the term *match* to refer to the behavior of
what Python has always called :func:`~re.search`.
See :ref:`prefixmatch-vs-match`.


.. function:: fullmatch(pattern, string, flags=0)
Expand Down Expand Up @@ -1313,12 +1313,12 @@ Regular Expression Objects
with older Python versions.

.. versionchanged:: next
An alternate :meth:`~Pattern.prefixmatch` name with this API was added as
a more descriptive explicit name for the behavior of
:meth:`~Pattern.match`. Use it to more clearly express intent. The norm
in other languages and regular expression implementations is to use the
term *match* to refer to the behavior of what Python has always called
:meth:`~Pattern.search`. See :ref:`prefixmatch-vs-match`.
The alternate :meth:`~Pattern.prefixmatch` name of this API was added as
a more explicitly descriptive name than :meth:`~Pattern.match`. Use it to
better express intent. The norm in other languages and regular expression
implementations is to use the term *match* to refer to the behavior of
what Python has always called :meth:`~Pattern.search`.
See :ref:`prefixmatch-vs-match`.


.. method:: Pattern.fullmatch(string[, pos[, endpos]])
Expand Down Expand Up @@ -1784,6 +1784,7 @@ this old Python gotcha.

We **do not** plan to deprecate and remove the older *match* name,
as it has been used in code for over 30 years.
Code supporting older versions of Python should continue to use *match*.

.. versionadded:: next

Expand Down
Loading