GeezerVison is showing github.com — gh-95913: Edit & expand Deprecated section of 3.11 WhatsNew by CAM-Gerlach · Pull Request #98581 · python/cpython
Conversation
CAM-Gerlach
commented
Oct 24, 2022
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
Part of #95913
This PR copyedits, Sphinxifies, organizes and formats the Deprecated (Python) section in the Python 3.11 What's New. Specifically, it:
- Organizes the section from a long, flat, essentially arbitrary list of items to be ordered by Language/Builtin deprecations, then whole Module deprecation, and finally deprecations in the stdlib, sorted alphabetically. This puts the broader-reaching changes nearer the top and makes it much easier for readers to navigate and find particular areas/deprecations they are interested in.
- Formats the listing of PEP 594-removed modules from a long thin bulleted list to a table, to take up much less space while being easier to skim at a glance
- Tweaks the text to fix grammar and phrasing errors and issues
- Fixes and enhances the Sphinx cross-references and reST syntax used
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:
importlib.resources deprecated its original set of functions added in 3.7 and supplanted by improved alternatives in 3.9. However, that hadn't been mentioned in the What's New anywhere I could find, so I added a short description and enumerated the relevant functions.
There may be more in the changelog that aren't properly documented in the docs, but if so that can wait for a followup.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Uh oh!
There was an error while loading. Please reload this page.
CAM-Gerlach reacted with thumbs up emoji
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, one wording suggestion
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
CAM-Gerlach reacted with thumbs up emoji
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this pull request
Oct 24, 2022
…thonGH-98581)
* Refine Sphinx syntax and grammar/phrasing in Deprecated section items
* Organize into lang/builtins, modules & stdlib sections
* Convert PEP 594 module list into a grid to not waste as much space
* Add importlib.resources deprecated functions to section
(cherry picked from commit dfb5d27)
Co-authored-by: C.A.M. Gerlach <[email protected]>
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
miss-islington
added a commit
that referenced
this pull request
Oct 24, 2022
* Refine Sphinx syntax and grammar/phrasing in Deprecated section items
* Organize into lang/builtins, modules & stdlib sections
* Convert PEP 594 module list into a grid to not waste as much space
* Add importlib.resources deprecated functions to section
(cherry picked from commit dfb5d27)
Co-authored-by: C.A.M. Gerlach <[email protected]>
Reviewers
jaraco
jaraco approved these changes
pablogsal
Awaiting requested review from pablogsal
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|