Skip to content

Add missing intersphinx prefixes to cross-references - #1937

Closed
summeriver13 wants to merge 2 commits into
python:mainfrom
summeriver13:fix/intersphinx-refs
Closed

summeriver13 wants to merge 2 commits into
python:mainfrom
summeriver13:fix/intersphinx-refs

Conversation

@summeriver13

Copy link
Copy Markdown

Seven :ref: targets render as plain text instead of links: the labels live in the CPython docs and the python: intersphinx prefix is missing.

Checked on https://devguide.python.org — each shows up as <span class="xref std std-ref"> with no href:

  • developer-workflow/extension-modules/: "Stable ABI", "Limited API"
  • development-tools/clinic/howto/: "Limited API", "heap type", "C "converter function""
  • development-tools/clinic/: "Limited API" (under --limited)
  • documentation/start-documenting/: "tracker"

All seven targets already exist in the CPython docs, so only the prefix changes:

label defined in
stable-abi, limited-c-api Doc/c-api/stable.rst:54, :443
heap-types Doc/c-api/typeobj.rst:2586
o_ampersand Doc/c-api/arg.rst:333
reporting-bugs Doc/bugs.rst:1

c-api.rst already reaches the stability page via python:stable. With nitpicky = True these seven are currently "undefined label" warnings, tolerated only because --fail-on-warning is commented out in the Makefile.

No wording changes, no new labels.

AI assistance: drafted with deepseek-v4.1-flash in the pi coding agent; each claim re-checked against the live site HTML and the CPython sources.

Seven :ref: targets in the extension, clinic, and documentation pages resolved to nothing because their labels live in the CPython docs. Prefix them with the python: intersphinx name.
@python-cla-bot

python-cla-bot Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

All commit authors signed the Contributor License Agreement.

CLA signed

@StanFromIreland

Copy link
Copy Markdown
Member

These are fine, Sphinx resolves all of the labels, for example:

image

As such, I'm going to close.

@summeriver13

Copy link
Copy Markdown
Author

You're right, sorry — I misread the HTML: the xref std std-ref span sits inside the <a href=...>, so all seven resolve fine. Thanks for checking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants