Jim HesterThis thread (https://discuss.python.org/t/formalize-the-concept-of-soft-deprecation-dont-schedule-removal-in-pep-387-backwards-compatibility-policy/27957/84 ) discussing the new “soft depreciation” in python is an interesting read after having conversations about very similar ideas and coming up with ‘superseded’ a few years ago in the tidyverse (this is eventually brought up and linked in the discussion)
Formalize the concept of "soft deprecation" (don't schedule removal) in PEP 387 "Backwards Compatibility Policy"
Over the last years, IMO the quality of instructions to get rid of deprecated and removed functions improved in What’s New In Python documents. Sure, there is always room for enhancement, and contributions are welcomed 🙂 Recently, I enhanced imp removal docs (Python 3.12) to provide recipes to replace removed APIs. The most difficult part is to provide a solution working on old and new Python versions. If possible, a solution for that should always be provided.