This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients ezio.melotti, gregory.p.smith, mrabarnett, serhiy.storchaka
Date 2020-11-14.18:22:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1605378166.26.0.0857474108222.issue42353@roundup.psfhosted.org>
In-reply-to
Content
My point is that re.match is a common bug when people really want re.search.

re.prefixmatch makes it explicit and non-confusing and thus unlikely to be used wrong or misunderstood when read or reviewed.

The term "match" when talking about regular expressions is not normally meant to imply any anchoring as anchors can be expressed within the regex.  Python is relatively unique in bothering to have different methods for a prefix match and an anywhere match.  (We'd have been better off without a match method entirely, only having search - too late now)
History
Date User Action Args
2020-11-14 18:22:46gregory.p.smithsetrecipients: + gregory.p.smith, ezio.melotti, mrabarnett, serhiy.storchaka
2020-11-14 18:22:46gregory.p.smithsetmessageid: <1605378166.26.0.0857474108222.issue42353@roundup.psfhosted.org>
2020-11-14 18:22:46gregory.p.smithlinkissue42353 messages
2020-11-14 18:22:46gregory.p.smithcreate