Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Add a guide to deprecating features #1469

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
Lincoln-developer wants to merge 11 commits into
base: main
Choose a base branch
from
Draft

Add a guide to deprecating features #1469

Changes from 1 commit
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
f2fd360
Added deprecation workflow in CPython.
Lincoln-developer Nov 8, 2024
e99387d
Fixed sphinx-linting error
Lincoln-developer Nov 8, 2024
be9224b
Update developer-workflow/cpython-deprecation-workflow.rst
Lincoln-developer Nov 8, 2024
b8fbd0b
Update developer-workflow/cpython-deprecation-workflow.rst
Lincoln-developer Nov 8, 2024
207294f
Update developer-workflow/cpython-deprecation-workflow.rst
Lincoln-developer Nov 8, 2024
a90e99a
Update developer-workflow/cpython-deprecation-workflow.rst
Lincoln-developer Nov 8, 2024
fc0b4ec
Update developer-workflow/cpython-deprecation-workflow.rst
Lincoln-developer Nov 8, 2024
7029868
Update developer-workflow/cpython-deprecation-workflow.rst
Lincoln-developer Nov 8, 2024
0dc75ec
Update developer-workflow/cpython-deprecation-workflow.rst
Lincoln-developer Nov 8, 2024
0d8bd61
fixed requested changes
Lincoln-developer Nov 8, 2024
d077a58
fixed required warning function
Lincoln-developer Nov 11, 2024
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
fixed required warning function
  • Loading branch information
@Lincoln-developer
Lincoln-developer committed Nov 11, 2024
commit d077a584de16c84e2a296ff18ff8a70b5d739ab2
2 changes: 1 addition & 1 deletion developer-workflow/cpython-deprecation-workflow.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ Deprecation implementation

Once approved:

* **Raise a Warning**: Use :func:`warnings.warn` with :exc:`DeprecationWarning` for typical cases.
* **Raise a Warning**: Use ``warnings._deprecated`` with :exc:`DeprecationWarning` for typical cases.
Copy link
Copy Markdown
Member

@StanFromIreland StanFromIreland Sep 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this preferred over the documented and more common warnings.warn (over 3x in the stdlib)?

If the feature is in its early deprecation phase:

* Use :exc:`PendingDeprecationWarning` initially, which transitions to :exc:`DeprecationWarning` after a suitable period.
Copy link
Copy Markdown
Member

@StanFromIreland StanFromIreland Sep 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We rarely use PendingDeprecationWarning, I think we can drop it?

Expand Down