Repository navigation
DOC: update sphinx and numpydoc pins #30684
Description
Currently sphinx and numpydoc are pinned to old versions in the requirements file:
numpy/requirements/doc_requirements.txt
Lines 2 to 3 in 90f6cc1
Numpydoc 1.4 is from 2022 and Sphinx 7.2.6 is from 2023.
It would behoove us to update these to the current versions so our documentation build configuration doesn't hopelessly bitrot.
I tried updating these pins in #30683 but punted when the update proved nontrivial. The build does succeed, but with more than a thousand warnings: https://gist.github.com/ngoldbaum/ad5e476401a591d378df406e2bcfaada
#28694 is related too - that's using a sphinx version newer than our pin.
Reacted by Sebastian Berg and Inessa Pawson
Activity
shiragemalashri-shri commentedon Feb 6, 2026
Hi, I’d like to work on this issue if it’s still available.
I will locate the incorrect indentation, fix it, and ensure
the documentation builds correctly. Please let me know if this
approach is fine. Thanks!
AbhiRKeesara commentedon Sep 25, 2026
Hi Team,
Seems
numpydocis updated to latest version1.11.0with this #32699 PR. I'll try to getSphinxto latest version9.1.0to close out this issue.Thanks!
AbhiRKeesara commentedon Sep 25, 2026
Hi Team,
I investigated updating the sphinx pin from 8.2.3 to 9.1.0.
sphinx 9.1.0 has an upstream regression that breaks the NumPy docs build. It produces about 357 warnings like:
This affects all ufuncs (C extension types). The bug is in Sphinx 9's rewritten autodoc. It assumes the signatures list is non-empty, but for C extensions where numpydoc provides the signature via hook, the list starts empty.
Setting
autodoc_use_legacy_class_based = True(the official workaround per sphinx-doc/sphinx#14089) only reduces warnings from 586 to 451. The remaining 224 come fromautosummary, which bypasses the legacy flag.I reported the specific bug to sphinx-doc/sphinx#14089. Seems like this issue has to be parked until then.
Thanks!