# PEP 816: WASI support **URL:** \ **Category:** PEPs\ **Created:** [December 8, 2025, 7:31pm UTC](https://discuss.python.org/t/pep-816-wasi-support/105237 "2025-12-08T19:31:22Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![brettcannon](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/brettcannon/32/34895_2.png) [@brettcannon](https://discuss.python.org/u/brettcannon)\ **Post date:** [December 8, 2025, 7:31pm UTC](https://discuss.python.org/t/pep-816-wasi-support/105237/1 "2025-12-08T19:31:22Z")
> **[PEP 816 – WASI Support | peps.python.org](https://peps.python.org/pep-0816/)** > > This PEP outlines the expected support for WASI by CPython. It contains enough details to know what WASI and WASI SDK version is expected to be supported for any release of CPython while official WASI support is specified in PEP 11. 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. ---
**Author:** ![brettcannon](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/brettcannon/32/34895_2.png) [@brettcannon](https://discuss.python.org/u/brettcannon)\ **Post date:** [January 9, 2026, 8:05pm UTC](https://discuss.python.org/t/pep-816-wasi-support/105237/2 "2026-01-09T20:05:36Z")
Thanks for the hearts! I’ve [sent this to the SC](https://github.com/python/steering-council/issues/329). ---
**Author:** ![corona10](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/corona10/32/9943_2.png) [@corona10](https://discuss.python.org/u/corona10)\ **Post date:** [February 27, 2026, 2:23am UTC](https://discuss.python.org/t/pep-816-wasi-support/105237/3 "2026-02-27T02:23:45Z")
Hi Brett, On behalf of the Steering Council, I’m pleased to inform you that [PEP 816](https://peps.python.org/pep-0816/) has been approved. Congratulations! However, we would like the PEP to clarify who bears the responsibility of keeping [PEP 11](https://peps.python.org/pep-0011/) 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) ---
**Author:** ![brettcannon](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/brettcannon/32/34895_2.png) [@brettcannon](https://discuss.python.org/u/brettcannon)\ **Post date:** [February 27, 2026, 11:39pm UTC](https://discuss.python.org/t/pep-816-wasi-support/105237/4 "2026-02-27T23:39:03Z")
> [@corona10](#): > > I’m pleased to inform you that [PEP 816](https://peps.python.org/pep-0816/) has been approved. Congratulations! Thanks so much! > [@corona10](#): > > we would like the PEP to clarify who bears the responsibility of keeping [PEP 11](https://peps.python.org/pep-0011/) up to date Me and any other people listed in PEP 11 as maintaining WASI. > [@corona10](#): > > when this is done (when the build scripts are updated, or on release of beta 1, or at some other point of time). I was thinking around beta 1. ---
**Author:** ![brettcannon](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/brettcannon/32/34895_2.png) [@brettcannon](https://discuss.python.org/u/brettcannon)\ **Post date:** [March 1, 2026, 4:48am UTC](https://discuss.python.org/t/pep-816-wasi-support/105237/5 "2026-03-01T04:48:34Z")
[PEP 816: Address SC requests and mark as Active by brettcannon · Pull Request #4836 · python/peps · GitHub](https://github.com/python/peps/pull/4836) 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).