-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
PEP 621: Remove invalid reference #3564
Conversation
The reference is not rendered, not used, and it doesn't exist.
PEP 639 and PEP 739 point to https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ ... which is now a HTTP 404 "Not Found" error. |
This change fix a build error on my PR #3560:
|
We shouldn't delete canonical links to specs. Please see #3563 which fixes it instead :) |
I'm not sure why Sphinx decided to emit a new warning. On the previous commit, the "Render PEPs" job didn't emit a warning: https://github.com/python/peps/actions/runs/7075200705/job/19257061142 sphinx-build was already run with Before (success), versions:
On my PR, when the job failed, versions: same versions!
|
Because we use intersphinx, which loads references from other Sphinx websites, in this case https://packaging.python.org. Last night they merged a re-org which deleted a reference we were using. |
More on intersphinx: https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html We also use it to load references from CPython docs and the devguide, see these lines in the logs:
|
Oh, I didn't know this Sphinx feature. |
The reference is not rendered, not used, and it doesn't exist.
📚 Documentation preview 📚: https://pep-previews--3564.org.readthedocs.build/