Conversation
|
This fix is not correct, I'll update this PR when I can use my computer. |
ghost
changed the title
serhiy-storchaka
added
type-bug
|
@serhiy-storchaka |
There was a problem hiding this comment.
Why search() is used instead of match() or fullmatch()?
ab|a is equivalent to ab?. Is there a reason why use the former? If there is a difference, it is better to use .b|a instead, because ab|a can be transformed to ab? by the RE compiler in future versions.
There was a problem hiding this comment.
Nice catch, this PR doesn't fix the problem.
>>> re.match(r'(ab?)*?b', 'ab').groups()
('',)
The correct output should be:
>>> regex.match(r'(ab?)*?b', 'ab').groups()
('a',)
I will recheck the patch tomorrow.
There was a problem hiding this comment.
Why
search()is used instead ofmatch()orfullmatch()?
ab|ais equivalent toab?. Is there a reason why use the former?
"Because it can be". (ab|a)*?b is a reduced test case for a real regex I found during my research.
There was a problem hiding this comment.
X{0,}? is equivalent to X*?, so this test is redundant.
ghost
changed the title
Show the wrong behaviors before this fix.
MARK_PUSH(lastmark) macro didn't protect MARK-0 if it was the only available mark.
ghost
changed the title
before this fix, the test-case returns ('c', 'c', 'c')
No need to save state->repeat in ctx->u.rep.
SRE_OP_BRANCH saves state->repeat in ctx->u.rep, this is because after JUMP_BRANCH, the state->repeat may be NULL.
While SRE_OP_ASSERT_NOT doesn't have this problem.
|
GH-12134 is a backport of this pull request to the 2.7 branch. |
|
See PR 12427 |
ghost
closed this
5 participants
Fix wrong capturing groups in rare cases, the span of capturing group may be lost when backtracking.
These bugs exist since Python 2.
MARK_PUSH(lastmark)didn't protectMARK 0if it was the only available markJUMP_MIN_UNTIL_3needsLASTMARK_SAVE()andMARK_PUSH()JUMP_ASSERT_NOTneedsLASTMARK_SAVE()andMARK_PUSH()Please read review guide in issue35859:
https://bugs.python.org/issue35859