Skip to content
Merged
Changes from 1 commit
Commits
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
Prev Previous commit
PEP 101: Remove manual step to add 'superseded by' notes to all old p…
…ages
  • Loading branch information
hugovk committed Nov 26, 2025
commit f19b65f344793c86961ebadc76770cd873093660
16 changes: 0 additions & 16 deletions peps/pep-0101.rst
Original file line number Diff line number Diff line change
Expand Up @@ -646,22 +646,6 @@ permissions.

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

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

- 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/>`_.

- 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