Skip to content

gh-4379: Link target release to release PEP in PEP 0#5058

Open
BHUVANSH855 wants to merge 1 commit into
python:mainfrom
BHUVANSH855:fix-4379-pep0-release-links
Open

gh-4379: Link target release to release PEP in PEP 0#5058
BHUVANSH855 wants to merge 1 commit into
python:mainfrom
BHUVANSH855:fix-4379-pep0-release-links

Conversation

@BHUVANSH855

Copy link
Copy Markdown

Summary

This change links Python version entries in PEP 0 to their corresponding release schedule PEPs.

Specifically, it:

  • Builds a mapping from Python versions to release schedule PEP numbers using release-topic metadata.
  • Emits :pep: references for Python version entries when a matching release schedule PEP exists.
  • Falls back to plain text when no matching release schedule PEP is available.
  • Adds a regression test covering the new linking behavior.

Testing

python -m pytest
python build.py

Results:

  • 532 passed, 2 xfailed
  • Documentation build succeeded

Issue

Closes #4379

@BHUVANSH855
BHUVANSH855 requested a review from AA-Turner as a code owner July 25, 2026 15:12
@read-the-docs-community

Copy link
Copy Markdown

Documentation build overview

📚 pep-previews | 🛠️ Build #33757148 | 📁 Comparing bfc2b35 against latest (9bb3132)

  🔍 Preview build  

4 files changed
± index.html
± numerical/index.html
± pep-0000/index.html
± pep-0764/index.html

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.

Link target release to release PEP in PEP 0

1 participant