# \`wasm32-emscripten\` and \`wasm32-wasi\` have been promoted to tier 3 platforms for CPython

**URL:** <https://discuss.python.org/t/wasm32-emscripten-and-wasm32-wasi-have-been-promoted-to-tier-3-platforms-for-cpython/17590>\
**Category:** WebAssembly\
**Created:** [July 22, 2022, 7:27pm UTC](https://discuss.python.org/t/wasm32-emscripten-and-wasm32-wasi-have-been-promoted-to-tier-3-platforms-for-cpython/17590 "2022-07-22T19:27:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**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:** [July 22, 2022, 7:27pm UTC](https://discuss.python.org/t/wasm32-emscripten-and-wasm32-wasi-have-been-promoted-to-tier-3-platforms-for-cpython/17590/1 "2022-07-22T19:27:34Z")

</div>

> **[PEP 11 – CPython platform support | peps.python.org](https://peps.python.org/pep-0011/#tier-3)**
>
> Python Enhancement Proposals (PEPs)

What this effectively means is people can’t rip out WebAssembly support from CPython.

The hope is we can hit tier 2 in October, which would mean WebAssembly support will block releases if it’s broken. Since it would be the first platform promoted to tier 2 since the tiers were introduced, I don’t know what will exactly be required beyond the [WebAssembly buildbot](https://buildbot.python.org/all/#/workers/58) saying up and stable along with supporting WebAssembly not being a massive burden. My suspicion is any other requirements will simply be due to trailblazing such a promotion and not specific WebAssembly.

---

<div class="post-metadata">

**Author:** ![bjkeefe](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/bjkeefe/32/4660_2.png) [@bjkeefe](https://discuss.python.org/u/bjkeefe)\
**Post date:** [July 27, 2022, 5:00pm UTC](https://discuss.python.org/t/wasm32-emscripten-and-wasm32-wasi-have-been-promoted-to-tier-3-platforms-for-cpython/17590/2 "2022-07-27T17:00:16Z")

</div>

Further down that same PEP 11 page is a pleasurable (mostly!) [stroll down memory lane](https://peps.python.org/pep-0011/#no-longer-supported-platforms). So, thanks for that, also.

---

<div class="post-metadata">

**Author:** ![tiran](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/tiran/32/48_2.png) [@tiran](https://discuss.python.org/u/tiran)\
**Post date:** [July 27, 2022, 6:53pm UTC](https://discuss.python.org/t/wasm32-emscripten-and-wasm32-wasi-have-been-promoted-to-tier-3-platforms-for-cpython/17590/3 "2022-07-27T18:53:39Z")

</div>

The `configure` script and [buildbots](https://buildbot.python.org/all/#/builders?tags=%2B3.x&tags=%2Btier-3) have been updated to report both new platforms as tier 3 platforms.

`checking for PEP 11 support tier... wasm32-unknown-wasi/clang has tier 3`  
`checking for PEP 11 support tier... wasm32-unknown-emscripten/clang has tier 3`