PEP 816: WASI support

PEPs
1

The executive summary is:

  • Lock down WASI and WASI SDK version support at b1 for the life of a Python version and write it down in PEP 11
  • Changes to the WASI SDK version after b1 requires writing down why
  • Changes to the WASI version require SC approval
  • Updating the target triple for main in PEP 11 doesn’t require anything special.

I’ve cleared this with the appropriate folks at the Bytecode Alliance and our current and future RMs are aware of it.

14 Likes
PEP specifying WASI support
2

Thanks for the hearts! I’ve sent this to the SC.

3

Hi Brett,

On behalf of the Steering Council, I’m pleased to inform you that PEP 816 has been approved. Congratulations!

However, we would like the PEP to clarify who bears the responsibility of keeping PEP 11 up to date, and when this is done (when the build scripts are updated, or on release of beta 1, or at some other point of time).

Thank you for your patience and for your work on this.

Warm regards,
Donghee
(on behalf of the Python Steering Council)

6 Likes
2026-02-26 PSC Meeting Summary
4

Thanks so much!

Me and any other people listed in PEP 11 as maintaining WASI.

I was thinking around beta 1.

3 Likes
5

PEP 816: Address SC requests and mark as Active by brettcannon · Pull Request #4836 · python/peps · GitHub has the changes and marks the PEP as Active (unless it should be Final; but I figure since it has rules to apply going forward that Active was a better fit).

2 Likes