# I'm stepping down as sponsor of Emscripten

**URL:** <https://discuss.python.org/t/im-stepping-down-as-sponsor-of-emscripten/41064>\
**Category:** WebAssembly\
**Created:** [December 14, 2023, 12:57am UTC](https://discuss.python.org/t/im-stepping-down-as-sponsor-of-emscripten/41064 "2023-12-14T00:57:43Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![encukou](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/encukou/32/2461_2.png) [@encukou](https://discuss.python.org/u/encukou)\
**Post date:** [January 31, 2024, 9:14am UTC](https://discuss.python.org/t/im-stepping-down-as-sponsor-of-emscripten/41064/21 "2024-01-31T09:14:35Z")

</div>

> [@encukou](#):
>
> Improving CPython project processes (figuring out how community support for a platform _should_ work)

See here:

> [@Community support for a platform](https://discuss.python.org/t/community-support-for-a-platform/44621):
>
> Continuing the discussion from [Proposed update to PEP-11 on Unsupporting a platform (less draconian measures)](https://discuss.python.org/t/proposed-update-to-pep-11-on-unsupporting-a-platform-less-draconian-measures/44065/9): And does it matter to them? We handle/close issues based on whether a volunteer wants to work on them. IMO, PEP-11 is mostly a summary of what we want to work on, written for Python devs/triagers – so that you know who to bug for a particular platform, or whether you should “revert first and fix later” when something goes red. For users, there’s very little actionable information in …

---

<div class="post-metadata">

**Author:** ![hoodmane](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/hoodmane/32/4037_2.png) [@hoodmane](https://discuss.python.org/u/hoodmane)\
**Post date:** [January 31, 2024, 5:40pm UTC](https://discuss.python.org/t/im-stepping-down-as-sponsor-of-emscripten/41064/22 "2024-01-31T17:40:34Z")

</div>

> To be clear, I’ll be happy to help with things like: …

Thanks @encukou, we really appreciate it!

---

<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:** [January 31, 2024, 11:50pm UTC](https://discuss.python.org/t/im-stepping-down-as-sponsor-of-emscripten/41064/23 "2024-01-31T23:50:19Z")

</div>

> [@encukou](#):
>
> I will assume @hoodmane, @rth, @ryanking13 can speak for Pyodide, and @pmp-p is interested in Emscripten too. So let’s ping y’all and wait for your opinions when it comes to Emscripten/browser support.

FYI I’m hoping to remove Emscripten references from the docs for Python 3.13.

I also plan to drop Emscripten-related files in [cpython/Tools/wasm at main · python/cpython · GitHub](https://github.com/python/cpython/tree/main/Tools/wasm) that are not being used by a buildbot to make sure they are still working in Python 3.14 (since it’s mostly helper scripts I don’t think it will be that impactful).

---

<div class="post-metadata">

**Author:** ![encukou](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/encukou/32/2461_2.png) [@encukou](https://discuss.python.org/u/encukou)\
**Post date:** [February 1, 2024, 8:38am UTC](https://discuss.python.org/t/im-stepping-down-as-sponsor-of-emscripten/41064/24 "2024-02-01T08:38:29Z")

</div>

People interested in supporting Emscripten are now listed in the [Experts index](https://devguide.python.org/core-developers/experts/#platforms).

I suggest treating this as _handing over_ platform support to projects like Pyodide, rather than dropping it :‍)

[Previous page](https://discuss.python.org/t/im-stepping-down-as-sponsor-of-emscripten/41064.md?page=1)