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 brandtbucher
Recipients Mark.Shannon, ammar2, brandtbucher, nedbat
Date 2021-07-15.18:47:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1626374859.84.0.837663298304.issue44600@roundup.psfhosted.org>
In-reply-to
Content
Thanks, that test framework looks good for this.

My initial hunch (just from looking at this) is that this has to do with how we handle cleanup after failed matches. Our "fail pop" blocks probably have whatever the last line number compiled was (which I think is always the last line of the preceding case block).

The fix *should* be as simple as calling "SET_LOC(c, whatever_the_last_pattern_was)" before compiling these blocks.

I have some new-ish contributors who might want to take this. As far as compiler issues go, this one seems pretty straightforward.
History
Date User Action Args
2021-07-15 18:47:39brandtbuchersetrecipients: + brandtbucher, nedbat, Mark.Shannon, ammar2
2021-07-15 18:47:39brandtbuchersetmessageid: <1626374859.84.0.837663298304.issue44600@roundup.psfhosted.org>
2021-07-15 18:47:39brandtbucherlinkissue44600 messages
2021-07-15 18:47:39brandtbuchercreate