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
Breaking API change for nitpick_ignore #11355
Comments
Could you change A |
We can definitely update our code, but that won't help anyone who has currently released versions of Matplotlib and try to build the docs with the latest version of sphinx. |
To be clear, even if you do wish to allow set and tuple, changing the default back to list would at least mitigate effects felt by our (and any similiar) extensions. At that point, only new users using the new features would run into problems with extensions that cannot handle sets or tuples. We can fix mpl's internal usage by even simply explicitly setting |
The question from Sphinx's perspective is if the internal type of I think reasonable to make A |
I've released Sphinx 6.2.1 with a fix for this. cc: @ksunden; @tacaswell A |
Thank you @AA-Turner ! |
Describe the bug
The change from a list to a set is a breaking API change which affects Matplotlib's sphinx build. We have an extension which expects this value to be a list (with the
extend
method thereof)How to Reproduce
conf.py:
index.rst:
missing_references.json:
sphinxext/missing_references.py:
Copied from matplotlib
Errors because it is expecting
app.conf.nitpick_ignore
to be a list, not a set.Environment Information
Sphinx extensions
Additional context
Link to failing mpl doc build: https://app.circleci.com/pipelines/github/matplotlib/matplotlib/23801/workflows/28a233c0-3582-42a8-99fc-164922a2fe7a/jobs/75765
The line from sphinx:
sphinx/sphinx/config.py
Line 135 in 60d8fa1
The commit where it changed:
7ecf037
The text was updated successfully, but these errors were encountered: