classification
Title: An extended definition of "non-overlapping" would save time.
Type: enhancement Stage:
Components: Documentation Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: rhettinger Nosy List: foolip, rhettinger
Priority: normal Keywords:

Created on 2003-05-04 09:56 by foolip, last changed 2003-08-31 05:31 by rhettinger. This issue is now closed.

Messages (2)
msg15861 - (view) Author: Philip Jägenstedt (foolip) Date: 2003-05-04 09:56
Hello.

Yesterday I spent several hours trying to figure out
why a (stupid) regex like "^|foo" didn't return ['',
'foo'] for findall("foo").

Like this:

|f|o|o|
0 1 2 3

I figured the ^ would match 0-0 and then a 0-3 match
for foo. I've learnt since that the reason this can't
happen is because the regexp engine would get caught in
an infinte loop. However, the two matches aren't really
overlapping, and the docs state that all
non-overlapping matches would be returned.

I suggest therefor that it is clarified in the docs
that non-overlapping doesn't apply to a zero-length
match at the beginning of another potential match.

This would apply to findall and finditer in
doc/python2.2/html/lib/node99.html.
msg15862 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2003-08-31 05:31
Logged In: YES 
user_id=80475

Nice catch.

Applied fix to Doc/lib/libre.tex 1.103 and  1.101.8.2
History
Date User Action Args
2003-05-04 09:56:57foolipcreate