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
MAINT, DOC: CI failure for doc building #14911
Comments
* temporary workaround for scipygh-14911 to see if it gets CI doc build green again
We might ask matplotlib folks about this. I think pyparsing is just the interim for the raised Error. |
Probably true, it is an indirect dependency--I guess that's what I meant about temporary pin if it works/is even worth pinning. |
Indeed, we can also play nice with the TeX syntax via |
Pinning an indirect dependency is a little annoying, because there's no good way to distinguish it from a direct dependency (except for a code comment). So let's just fix it straight away if we can - sounds like the TeX change will do that?
Yes, it's gotten worse is my impression ..... |
I missed that you already had a PR (gh-14912) up for this Tyler, thanks! So I merged that - let's just leave this open so we can get the root cause fixed and then revert the CI pin. |
@Smit-create is going to have a look at the fix for this issue this week. |
This seems to be working fine with pyparsing version |
Fixed by gh-14969 (or rather, by upstream stuff happening, so the pin was removed) |
I see the traceback below the fold in several unrelated PRs/merge event doc builds in the last day or two. The
pyparsing
library shows up in the error output, and I note that version3.0.0
was released on Oct. 23/2021 and3.0.1
just 5 hours ago. Before that, there were nothing but pre-releases going back to April 2020, so this seems like a decent candidate for the source of the error.We may want to temporarily pin
pyparsing
as an interim workaround.The text was updated successfully, but these errors were encountered: