FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

PEP 828: Supporting 'yield from' in asynchronous generators by ZeroIntensity · Pull Request #4854 · python/peps · GitHub

Repository navigation

PEP 828: Supporting 'yield from' in asynchronous generators - #4854

Merged
ZeroIntensity merged 12 commits into
python:mainfrom
ZeroIntensity:async-yield-from
Mar 9, 2026
Merged

ZeroIntensity merged 12 commits into
python:mainfrom
ZeroIntensity:async-yield-from

Conversation

ZeroIntensity commented Mar 8, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

I have intentionally not assigned this a number. I'm not totally sure whether I want to pursue this proposal as it stands, and/or if I should open a DPO thread first. I'm opening this to get initial reactions/feedback and to provide some rendered PEP text if I ask someone for opinions. I will assign this a number if I decide to continue with the proposal.


Basic requirements (all PEP Types)

  • Read and followed PEP 1 & PEP 12
  • File created from the latest PEP template
  • PEP has next available number, & set in filename (pep-NNNN.rst), PR title (PEP 123: <Title of PEP>) and PEP header
  • Title clearly, accurately and concisely describes the content in 79 characters or less
  • Core dev/PEP editor listed as Author or Sponsor, and formally confirmed their approval
  • Author, Status (Draft), Type and Created headers filled out correctly
  • PEP-Delegate, Topic, Requires and Replaces headers completed if appropriate
  • Required sections included
    • Abstract (first section)
    • Copyright (last section; exact wording from template required)
  • Code is well-formatted (PEP 7/PEP 8) and is in code blocks, with the right lexer names if non-Python
  • PEP builds with no warnings, pre-commit checks pass and content displays as intended in the rendered HTML
  • Authors/sponsor added to .github/CODEOWNERS for the PEP

Standards Track requirements

  • PEP topic discussed in a suitable venue with general agreement that a PEP is appropriate
  • Suggested sections included (unless not applicable)
    • Motivation
    • Specification
    • Rationale
    • Backwards Compatibility
    • Security Implications
    • How to Teach This
    • Reference Implementation
    • Rejected Ideas
    • Open Issues
    • Acknowledgements
    • Footnotes
    • Change History
  • Python-Version set to valid (pre-beta) future Python version, if relevant
  • Any project stated in the PEP as supporting/endorsing/benefiting from the PEP formally confirmed such
  • Right before or after initial merging, PEP discussion thread created and linked to in Discussions-To and Post-History

📚 Documentation preview 📚: https://pep-previews--4854.org.readthedocs.build/pep-0828/

Rosuav commented Mar 8, 2026

Copy link
Copy Markdown
Contributor

Probably worth opening a DPO thread. PEP looks good; not sure about targeting 3.15 but that can easily be changed later.

Copy link
Copy Markdown
Member Author

Comment thread peps/pep-9999.rst Outdated
johnslavik self-requested a review March 8, 2026 10:47

ZeroIntensity commented Mar 8, 2026 •
edited
Loading

Copy link
Copy Markdown
Member Author

The DPO thread showed some good initial reactions, and I received positive feedback from those I showed this to privately, so I've decided to continue with the proposal as it stands. I've assigned 828 as the PEP number.

ZeroIntensity changed the title PEP 9999: Supporting 'yield from' in asynchronous generators PEP 828: Supporting 'yield from' in asynchronous generators Mar 8, 2026
ZeroIntensity added the new-pep A new draft PEP submitted for initial review label Mar 8, 2026
ZeroIntensity marked this pull request as ready for review March 8, 2026 21:20
ZeroIntensity requested a review from a team as a code owner March 8, 2026 21:20
Comment thread peps/pep-0828.rst Outdated
Comment thread peps/pep-0828.rst Outdated
Comment thread peps/pep-0828.rst Outdated
Comment thread peps/pep-0828.rst Outdated

JelleZijlstra left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Looks good except for the minor issues noted above

Co-authored-by: Brian Schubert <brianm.schubert@gmail.com>
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>

johnslavik left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

At a glance looks very good!

Comment thread peps/pep-0828.rst

Copy link
Copy Markdown
Member Author

Thanks, everyone. I'm going to polish up the reference implementation a little bit more with @johnslavik, and then I'll merge this.

Comment thread peps/pep-0828.rst Outdated
Comment thread peps/pep-0828.rst Outdated
Comment thread peps/pep-0828.rst Outdated
Comment thread peps/pep-0828.rst
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
ZeroIntensity merged commit 863542d into python:main Mar 9, 2026
5 checks passed
ZeroIntensity deleted the async-yield-from branch March 9, 2026 17:47
ethanfurman pushed a commit to ethanfurman/peps that referenced this pull request Oct 8, 2026
)

Co-authored-by: Brian Schubert <brianm.schubert@gmail.com>
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
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

Labels

new-pep A new draft PEP submitted for initial review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants


Back | FazBrowse Home | New Git URL