PEP 512: Fix Sphinx reference warnings #4805
Merged
+0
−27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
All commit authors signed the Contributor License Agreement. |
Secrus
force-pushed
the
pep-512-warnings
branch
2 times, most recently
from
f565574 to
1c02064
Compare
brettcannon
approved these changes
Feb 3, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ref: #4087
The search for changes removing the references was done with:
git log --follow -S "<ref.footnote>" -p -- peps/pep-0512.rst.I have verified that PEP 512 generates no warnings on Sphinx v8.1.3.
📚 Documentation preview 📚: https://pep-previews--4805.org.readthedocs.build/