Sorry, something went wrong.
There was a problem hiding this comment.
Looks great. Thanks for taking the time to do this work. Did I miss an expected step when enacting the deprecation, or is this process working as expected?
Sorry, something went wrong.
|
Did I miss an expected step when enacting the deprecation, or is this process working as expected? The RMs are the ultimate authority, and I'm no authority at all, but at least nowadays, per the devguide and in general practice, it seems the What's New entry is supposed to be written as part of the deprecation PR. This it ensures it is prompt, accurate and doesn't fall through the cracks. I believe in the past, though, this may not have always been the case (based on the comments in the What's New document), and there was more responsibility on the RMs to trawl through the Changelog and write up items they thought were significant enough. In any case, thanks to the use of the deprecated/deprecated-removed directive and detailed-enough documentation, I was able to find and write it without too much trouble. |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good, one wording suggestion
Sorry, something went wrong.
|
Thanks @CAM-Gerlach for the PR, and @JelleZijlstra for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11. |
Sorry, something went wrong.
|
GH-98598 is a backport of this pull request to the 3.11 branch. |
Sorry, something went wrong.
Part of #95913
This PR copyedits, Sphinxifies, organizes and formats the Deprecated (Python) section in the Python 3.11 What's New. Specifically, it:
Also, searching through deprecation warnings in the docs, I found one set of deprecations that weren't documented in the What's New, and did so:
There may be more in the changelog that aren't properly documented in the docs, but if so that can wait for a followup.