Skip to content

PEP 816: WASI Support #4732

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.

Sign up for GitHub

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

Jump to bottom
Open
brettcannon wants to merge 10 commits into
base: main
Choose a base branch
from
Open

PEP 816: WASI Support #4732

brettcannon wants to merge 10 commits into from

Conversation

@brettcannon
Copy link
Member

@brettcannon brettcannon commented Dec 5, 2025 •
edited by github-actions bot
Loading

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
    • Rationale
    • Specification
    • Backwards Compatibility
    • Security Implications
    • How to Teach This
    • Reference Implementation
    • Rejected Ideas
    • Open Issues
  • 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--4732.org.readthedocs.build/

@brettcannon brettcannon self-assigned this Dec 5, 2025
@brettcannon brettcannon requested a review from a team as a code owner December 5, 2025 23:00
JelleZijlstra
JelleZijlstra approved these changes Dec 6, 2025
View reviewed changes
peps/pep-0816.rst
important so code works together.

This coordination and recording around version targets can be important in
situations where the selected versions is non-obvious. For example, WASI SDK 26
Copy link
Member

@JelleZijlstra JelleZijlstra Dec 6, 2025

Choose a reason for hiding this comment

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

Suggested change
situations where the selected versions is non-obvious. For example, WASI SDK 26
situations where the selected version is non-obvious. For example, WASI SDK 26

@AA-Turner AA-Turner added the new-pep A new draft PEP submitted for initial review label Dec 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@JelleZijlstra JelleZijlstra JelleZijlstra approved these changes

@hugovk hugovk hugovk approved these changes

Assignees

@brettcannon brettcannon

Labels

new-pep A new draft PEP submitted for initial review

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@brettcannon @JelleZijlstra @hugovk @AA-Turner