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
Sphinx test fails for myst-parser 0.18.0, works with myst-parser 0.17.2 #23598
Comments
These are the warnings
I don't understand where these warnings are coming from. It doesn't say what file is causing it. The things in question are attributes without documentation that don't seem to be referenced anywhere. It might be a bug in MyST. For now let's just pin MyST to a lower version so that the tests stop failing until we can figure out what is causing this. |
I've given some explanation here: Basically the Domain class has documented class attributes using attribute docstrings. Subclasses like Ring etc also set the attributes but since they don't use docstrings that doesn't show up in the docs. The update causes e.g. |
I've also opened an issue with myst-parser: |
The problem is Sphinx rather than myst-parser. Changing myst-parser just means that you end up with a different version of Sphinx. |
Ah, I thought this sounded more like a Sphinx (autodoc) bug than MyST. Does that mean that MyST pins Sphinx? At any rate, let's pin Sphinx until this gets an upstream fix released. |
Yes, looks like it's going to get fixed upstream: We should pin for now until there is a new release of Sphinx. |
This makes every PR fail.
The text was updated successfully, but these errors were encountered: