Greg Ewing greg.ewing at canterbury.ac.nz
Sat Oct 28 19:35:59 EDT 2017

• Previous message (by thread): [Python-Dev] \G (match last position) regex operator non-existant in python?
• Next message (by thread): [Python-Dev] \G (match last position) regex operator non-existant in python?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Guido van Rossum wrote:
> From this I understand that when using e.g. findall() it forces 
> successive matches to be adjacent.

Seems to me this would be better addressed using an option
to findall() rather than being part of the regex. That would
avoid the issue of where to keep the state.

-- 
Greg

---

• Previous message (by thread): [Python-Dev] \G (match last position) regex operator non-existant in python?
• Next message (by thread): [Python-Dev] \G (match last position) regex operator non-existant in python?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list