-
-
Notifications
You must be signed in to change notification settings - Fork 31k
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.
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
gh-95913: Prepare remaining Whatsnew sections for editing #98342
Merged
ezio-melotti
merged 4 commits into
python:main
from
CAM-Gerlach:whatsnew-add-linebreaks
Oct 18, 2022
Merged
gh-95913: Prepare remaining Whatsnew sections for editing #98342
ezio-melotti
merged 4 commits into
python:main
from
CAM-Gerlach:whatsnew-add-linebreaks
Oct 18, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CAM-Gerlach
added
3.11
only security fixes
needs backport to 3.11
only security fixes
labels
Oct 16, 2022
CAM-Gerlach
changed the title
bpo-95913: Prepare remaining Whatsnew sections for editing
gh-95913: Prepare remaining Whatsnew sections for editing
Oct 16, 2022
33 tasks
JelleZijlstra
approved these changes
Oct 16, 2022
5 tasks
ezio-melotti
approved these changes
Oct 18, 2022
Thanks @CAM-Gerlach for the PR, and @ezio-melotti for merging it 🌮🎉.. I'm working now to backport this PR to: 3.11. |
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this pull request
Oct 18, 2022
…onGH-98342) * Add line breaks & ref targets to Whatsnew to prepare for future changes * Use standard heading underbar symbols for H4 sections * Flatten Porting subsection; clarify scope of/link Python->CAPI sections * Move C API pending deprecations to C API section, to match the others (cherry picked from commit 0a0c7e5) Co-authored-by: C.A.M. Gerlach <[email protected]>
GH-98384 is a backport of this pull request to the 3.11 branch. |
miss-islington
added a commit
that referenced
this pull request
Oct 18, 2022
* Add line breaks & ref targets to Whatsnew to prepare for future changes * Use standard heading underbar symbols for H4 sections * Flatten Porting subsection; clarify scope of/link Python->CAPI sections * Move C API pending deprecations to C API section, to match the others (cherry picked from commit 0a0c7e5) Co-authored-by: C.A.M. Gerlach <[email protected]>
pablogsal
pushed a commit
that referenced
this pull request
Oct 22, 2022
* Add line breaks & ref targets to Whatsnew to prepare for future changes * Use standard heading underbar symbols for H4 sections * Flatten Porting subsection; clarify scope of/link Python->CAPI sections * Move C API pending deprecations to C API section, to match the others
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Part of #95913
To ensure PRs to edit the remaining sections can all be submitted in parallel and don't introduce any merge conflicts with each other, this preliminary PR (which can hopefully be merged quickly) ensures there are two line breaks between each section (per standard convention), and adds the same standard ref target labels to each section as the previous to enable stable cross-referencing.
To note, this PR does not do so for any of the
Improved Modules
subsections, which will be done in a separate PR once the current batch of PRs adding/editing those are merged, so the rest can safely proceed in parallel without conflicts.Additionally, it makes a few other straightforward but cross-cutting changes: