Two things.

One, can you add a directive to the docs like:

? That's what makes a module say "deprecated" in the module index.

Two, the SC wanted to leave out target removal versions in the docs in case we have to change something due to feedback (in the code itself via the warnings.warn call still makes sense). But since these modules were already deprecated and the community has not come back asking to save them I think specifying 3.12 is safe.

Two things.

One, can you add a directive to the docs like:

cpython/Doc/library/imp.rst

Line 6 in 099f756

:deprecated:

? That's what makes a module say "deprecated" in the module index.

Done!

Also added to the Superseded Modules page listing deprecated modules (imp is there), putting those needing most attention first (to be removed soonest, and most recently added).

Two, the SC wanted to leave out target removal versions in the docs in case we have to change something due to feedback (in the code itself via the warnings.warn call still makes sense). But since these modules were already deprecated and the community has not come back asking to save them I think specifying 3.12 is safe.

👍

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

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

Sorry @hugovk, I had trouble checking out the 3.9 backport branch.
Please backport using cherry_picker on command line.
cherry_picker 77473846439b8a3eae66de1a1cfe931619f38513 3.9

GH-31997 is a backport of this pull request to the 3.10 branch.

GH-31998 is a backport of this pull request to the 3.9 branch.