You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The cuda-bindings docs build succeeds but is not warning-free. The 13.5.0 release dry run reported 102 Sphinx warnings. Most are inherited from earlier releases, and not all 102 are necessarily distinct bugs.
Examples (not a complete list)
Failed autosummary imports:.rst catalog entries that name objects which cannot be imported (for example cu_memcpy in driver_v2.rst and several stale names in nvml.rst). Sphinx drops the entry and its detail page without leaving a visibly broken row.
Malformed reST and duplicate object descriptions reported in the Sphinx output.
Missing fragment targets on the legacy pages: 44 in total (34 driver, 10 runtime). They are broken back-references from problematic markup, including unescaped pointer asterisks. The same fragments are missing in the published 13.4.4 pages.
Plan of action
Baseline: save the complete Sphinx warning list from a clean docs build and group it by category (import failure, reST syntax, duplicate description, other).
Autosummary imports: fix or remove each entry that fails to import.
Markup: escape the pointer asterisks that produce the missing fragment targets, then fix the malformed reST.
Duplicates: resolve duplicate object descriptions, either by removing the redundant directive or by adding :no-index: where both are intentional.
Re-verify: rebuild, compare against the baseline, and record the remaining count and any warnings deliberately left.
Prevent regressions: once the count is near zero, make the docs build fail on new warnings (for example -W, or a recorded warning budget).
Activity
mdboom commentedon Nov 5, 2026
Most of this requires changes to the code generator to address, which will be complex to resolve.
In the meantime, #3387 handles the single non-generated fix we can apply to reduce the number of warnings.
docs: Put the v2 migration guide in a Migration guides toctree (#3387)