Skip to content

Conversation

@AA-Turner
Copy link
Member

@AA-Turner AA-Turner commented Nov 10, 2025

  • Change is either:
    • To a Draft PEP
    • To an Accepted or Final PEP, with Steering Council approval
    • To fix an editorial issue (markup, typo, link, header, etc)
  • PR title prefixed with PEP number (e.g. PEP 123: Summary of changes)

📚 Documentation preview 📚: https://pep-previews--4697.org.readthedocs.build/pep-0101/


- Update the `devguide
<https://github.com/python/devguide/blob/main/include/release-cycle.json>`__
- Update `python-releases.toml <../release_management/python-releases.toml>`__
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


- Update the `devguide
<https://github.com/python/devguide/blob/main/include/release-cycle.json>`__
- Update `python-releases.toml <../release_management/python-releases.toml>`__
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes a relative link on the web (e.g. https://pep-previews--4697.org.readthedocs.build/release_management/python-releases.toml), which isn't what we want. Best to remove the link, or just to link to GH instead?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hugovk snap again :)

What do you think of either of the above suggestions?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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