-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pyparsing 3.1.0 causing test failures in Markdown image inlining #293
Labels
bug
Something isn't working
Comments
The changelog has a few things it might be, but nothing that jumps out as for sure the issue. Going to bisect down to the specific beta release between 3.0.9 and 3.1.0. |
Something in 3.1.0b1, as 3.1.0a1 is ok. |
Ah, the issue is that
is now getting incorrectly parsed as:
i.e. with the title as part of the url attribute. That's not right! |
Bisected to pyparsing/pyparsing@9d789cb. |
tsibley
added a commit
that referenced
this issue
Jun 20, 2023
The recent release of pyparsing fixed a bug in SkipTo¹ "that has been there for a very very long time"² and which we were unintentionally relying upon. The fix caused our parsing of  to break as SkipTo(White()) no longer matched due to our grammar ignoring whitespace by default. We didn't notice until 3.1.0 was released a couple days ago. Explicitly don't ignore whitespace for this grammar element. This change is backwards compatible with older versions of pyparsing. Resolves <#293>. ¹ <pyparsing/pyparsing@9d789cbc> ² <pyparsing/pyparsing#475>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Failure started between our scheduled CI runs on Sunday (passing) and Monday (failing). The Python distributions installed (for the 3.7, Linux job) differ only in pyparsing version:
3.1.0 was released on Sunday, about 5 hours after our successful CI run.
Noticed this in #289 (comment).
The text was updated successfully, but these errors were encountered: