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 serhiy.storchaka
Recipients Gareth.Gouldstone, Lucretiel, ezio.melotti, mrabarnett, serhiy.storchaka
Date 2014-04-13.15:28:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <3748591.jtbvfHa361@raxxla>
In-reply-to <1396637374.23.0.844365787024.issue20998@psf.upfronthosting.co.za>
Content
> After stepping through the code for that regex that fails, I concluded
> that the condition shouldn't depend on ctx->match_all at that point
> after all.

Tests are passed without this check. But I'm not sure it is not needed. At 
least without this check the code is not equivalent to the code before adding 
support for fullmatch(). So I prefer to left it as is.

> I thought I'd initialised it in all the places it's used.
> 
> I admit that I find the code a little hard to follow at times... :-(

Indeed, it is initialized in Modules/_sre.c, and it is always 0. Perhaps it 
will be more consistent to get rid of the match_all field in the SRE_STATE 
structure and pass it as argument.
Files
File name Uploaded
issue20998_2.patch serhiy.storchaka, 2014-04-13.15:28:31
History
Date User Action Args
2014-04-13 15:28:32serhiy.storchakasetrecipients: + serhiy.storchaka, ezio.melotti, mrabarnett, Lucretiel, Gareth.Gouldstone
2014-04-13 15:28:32serhiy.storchakalinkissue20998 messages
2014-04-13 15:28:32serhiy.storchakacreate