PEP 798: Fixes and Clarifications from Discourse Thread #4518
Conversation
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
|
@JelleZijlstra, just a heads-up there are likely more changes to be made here (I haven't yet made any changes to address the concerns about regular versus async generators from the Discourse thread, for example, other than adding a link to PEP 525). |
JelleZijlstra
approved these changes
Aug 2, 2025
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.
This PR represents a few small wording changes for PEP 798 (primarily in the "How to Teach This" section) based on discussion from the Discourse thread, attempting to fix some correctness issues and to clarify some points. It also fixes syntax highlighting for the examples from other languages.
PEP 123: Summary of changes)📚 Documentation preview 📚: https://pep-previews--4518.org.readthedocs.build/