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

Skip to content
Draft
Changes from 1 commit
Commits
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
Next Next commit
Update developer-workflow/cpython-deprecation-workflow.rst
Co-authored-by: Adam Turner <[email protected]>
  • Loading branch information
Lincoln-developer and AA-Turner authored Nov 8, 2024
commit 0dc75ec7d1b2c340e38c9cb127e87ff9e963da24
7 changes: 4 additions & 3 deletions developer-workflow/cpython-deprecation-workflow.rst
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,8 @@ For gradual deprecations:
* Mention the pending deprecation in “What’s New.”
* No ``pending-removal-in`` entry is needed during this stage.

7. References and Templates
---------------------------
* Use ``.. deprecated::`` and ``.. removed::`` Sphinx roles for documentation.
References and templates
------------------------
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We can also link to PEP 4


* Use the ``.. deprecated-removed::`` roles for documentation.
* Add ``See Also`` links to :pep:`387` and DevGuide for policy and process details.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I don't understand, do you suggest a .. see-also:: under every deprecated feature?