GeezerVison

What happens if an entry from "Pending Removal in Future Versions" moves to "Pending Removal in Python 3.16"?
Would it be beneficial to include blank Doc/deprecations/pending-removal-in-3.*.rst up to when 3.13 will reach EOL (3.18)?

Then we move it from ../deprecations/pending-removal-in-future.rst into a .. include:: ../deprecations/pending-removal-in-3.16.rst.

Yes, but then it wouldn't show up in the list of future deprecations for 3.13 if 3.16 isn't included (which would be easy to forget when added).

Correct, when creating a new include file, you need to remember to add it to the relevant pages.

This only covers the C API, not the Python API. Is that intended?

TODO: This was meant to be for the Python deprecations, not C API ones. I'll update it.

What will we do with the C API? Do we include it like this? Or do we put it in a separate file?

.. include::  ../deprecations/pending-removal-in-3.14.rst
    :start-after: .. start_pending_removal_in_3_14_capi
    :end-before: .. end_pending_removal_in_3_14_capi

No, I think it would be easier to have each in their own files (not necessarily named like this):

deprecations/pending-removal-in-3.14.rst
deprecations/pending-removal-in-3.14_capi.rst

TODO: This was meant to be for the Python deprecations, not C API ones. I'll update it.

Updated.

Thanks @hugovk for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13.
🐍🍒⛏🤖

Sorry, @hugovk, I could not cleanly backport this to 3.13 due to a conflict.
Please backport using cherry_picker on command line.

cherry_picker a1df1b44394784721239615f307b273455536d14 3.13

GH-122038 is a backport of this pull request to the 3.13 branch.

I've opened #122085 as a tracking issue, and #122093 is the next PR.

GH-122038 is a backport of this pull request to the 3.13 branch.