Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Why python regexps look expecting a begin match, but not an ending one?

Post

Why python regexps look expecting a begin match, but not an ending one?

+4
−0

My impression is that the regexps behave a little bit odd:

>>> import re
>>> r=re.compile("test")
>>> r.match("test")
<re.Match object; span=(0, 4), match='test'>
>>> r.match("1test")
>>> r.match("test2")
<re.Match object; span=(0, 4), match='test'>
>>> r.match("1test2")
>>> 

I have also tried python-pcre, it behaves on the same way. If the "regexp" is only a single word, it should behave as a substring match (or a full-line match). It seems matching lines starting with "test", but not the ones ending with it (or containining it somewhere).

Why?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

About "why" questions in programming (and about the Q&A site model used on Codidact) (1 comment)
About "why" questions in programming (and about the Q&A site model used on Codidact)
Karl Knechtel‭ wrote about 15 hours ago

It's good to wonder why things are the way they are, as a programmer, but when it comes to "why does someone else's code work this way?" questions (including ones about the standard library), in general these aren't a good fit for a Q&A site because they don't offer insightful answers. Generally, the author of the other code simply had to make a choice, and only the author knows the reason for that choice - others can only speculate.

I think there's some reasonable speculation to do here, so I'll offer my own answer. But for the future, consider restricting "why" questions to the cases where you can't identify the underlying logic: i.e., you've reduced a problem to a simple example, and you get a result that isn't what you want, and you can't identify the pattern behind that result.

You'll notice that Michael's answer basically substituted a "how" question: "how do I get a substring match instead?".