Implementation of my proposed PEP 387 "Soft Deprecation" policy: https://github.com/python/peps/pull/3182 * Add SoftDeprecationWarning warning category * Ignore these warnings by default, except in the ``__main__`` module (similar to [PEP 565: Show DeprecationWarning in __main__](https://peps.python.org/pep-0565/)) As an example, I propose to soft deprecate the getopt module: PR #105735 (currently, the PR uses a regular "hard" deprecation). <!-- gh-linked-prs --> ### Linked PRs * gh-106142 <!-- /gh-linked-prs -->
Activity
pythongh-106137: Add SoftDeprecationWarning category
pythongh-106137: Add SoftDeprecationWarning category
pythongh-106137: Add SoftDeprecationWarning category
pythongh-106137: Add SoftDeprecationWarning category
pythongh-106137: Add SoftDeprecationWarning category
terryjreedy commentedon Jun 27, 2023
This seems like a new feature. Is there any discussion that you can link to? Such as about the PEP?
hugovk commentedon Jun 27, 2023
Discussion is ongoing at https://discuss.python.org/t/formalize-the-concept-of-soft-deprecation-dont-schedule-removal-in-pep-387-backwards-compatibility-policy/27957
vstinner commentedon Jun 27, 2023
Yes, see the first link in the issue :-)
=> python/peps#3182
Also, @hugovk gave the link to the discussion.
pythongh-106137: Add SoftDeprecationWarning category
pythongh-106137: Add SoftDeprecationWarning category
pythongh-106137: Add SoftDeprecationWarning category
pythongh-106137: Add SoftDeprecationWarning category
vstinner commentedon Jun 30, 2023
The idea of issuing a warning for soft deprecations is not liked, so I abandon my idea: https://discuss.python.org/t/formalize-the-concept-of-soft-deprecation-dont-schedule-removal-in-pep-387-backwards-compatibility-policy/27957