Skip to content

PEP 101: Remove three manual steps to edit python.org pages #4717

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.

Sign up for GitHub

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

Merged
merged 5 commits into from
Nov 26, 2025
+0 −45
Merged

PEP 101: Remove three manual steps to edit python.org pages #4717

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
60efb15
PEP 101: Remove manual step to edit pre-release page
hugovk Nov 25, 2025
8834c35
PEP 101: Remove manual step to edit docs page
hugovk Nov 26, 2025
bcd21a5
fixup! PEP 101: Remove manual step to edit pre-release page
hugovk Nov 26, 2025
18dc189
PEP 101: Remove manual step to edit https://www.python.org/doc/versions/
hugovk Nov 26, 2025
f19b65f
PEP 101: Remove manual step to add 'superseded by' notes to all old p…
hugovk Nov 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 0 additions & 45 deletions peps/pep-0101.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -646,51 +646,6 @@ permissions.

curl -X PURGE https://www.python.org/downloads/release/python-XXX/

- If this is a **final** release:

- Add the new version to the `"Python documentation by version"
page <https://www.python.org/doc/versions/>`__ and
remove the current version from any 'in development' section.

- For 3.X.Y, edit all the previous X.Y releases' page(s) to
point to the new release. This includes the content field of the
``Downloads -> Releases`` entry for the release::

Note: Python 3.x.(y-1) has been superseded by
`Python 3.x.y </downloads/release/python-3xy/>`_.

And, for those releases having separate release page entries
(phasing these out?), update those pages as well,
e.g. ``download/releases/3.x.y``::

Note: Python 3.x.(y-1) has been superseded by
`Python 3.x.y </download/releases/3.x.y/>`_.

- Update the `"Current pre-release testing versions" page
<https://www.python.org/download/pre-releases/>`__.

- If you're releasing a version before *3.x.0*,
add it to this page, removing the previous pre-release
of version *3.x* as needed.

- If you're releasing *3.x.0 final*, remove the pre-release
version from this page.

This is in the "Pages" category on the Django-based website, and finding
it through that UI is kind of a chore. However! If you're already logged
in to the admin interface (which, at this point, you should be), Django
will helpfully add a convenient "Edit this page" link to the top of the
page itself. So you can simply follow the link above, click on the
"Edit this page" link, and make your changes as needed. How convenient!

- If appropriate, update the `"Python documentation by version" page
<https://www.python.org/doc/versions/>`__.

This lists all releases of Python by version number and links to their
static (not built daily) online documentation. There's a link at the
bottom to the in-development version.
And yes you can press the shiny, exciting "Edit this page" button.

- Write the announcement on `discuss.python.org`_. This is the
fuzzy bit because not much can be automated. You can use an earlier
announcement as a template, but edit it for content!
Expand Down