PEP 818: Reduce number of details in spec - #4832
Merged
Merged
Conversation
According to Yhg1s there are too many implementation details here. This reduces them.
hoodmane
force-pushed
the
pep-818-shorten
branch
from
February 27, 2026 14:13
1dec129 to
3c6ca5a
Compare
Member
|
The 3.15 feature freeze has passed, would you also like to retarget |
Documentation build overview
|
freakboy3742
approved these changes
Oct 1, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
According to @Yhg1s there are too many implementation details here. This reduces them.
Does this look better to you @Yhg1s?
📚 Documentation preview 📚: https://pep-previews--4832.org.readthedocs.build/