Hi all,
On behalf of the Pyodide team, I would like to lay out a proposal
for the NumPy Steering Council to move the Emscripten/Pyodide platform
[1], currently listed at Tier 3 as per the provisions of the NumPy
Enhancement Proposal (NEP) 57 – "NumPy platform support" [2], up a
tier, to Tier 2. I have described my rationale for this proposal below, and
I would welcome any feedback. Please note that I have also added a
long-form writeup with additional information and context to support
this proposal in the following GitHub issue, which I would encourage you
to read:
https://github.com/numpy/numpy/issues/33365
Concretely, our request is for NumPy to publish one "pyemscripten" wheel
to PyPI, starting with NumPy 2.6.0 soon, or, perhaps within the 2.6.x
release cycle, if not the former. This would be a `cp314` wheel, for the
`pyemscripten_2026_0` platform. This platform is already currently
tested by NumPy in its release infrastructure. A `cp315` wheel, for the
`pyemscripten_2026_5` platform and an updated ABI, should follow later.
Our details about this are documented in the "Current status and
implementation plan" section of the full proposal, linked in the above
issue.
As per the NEP, one of the requirements stated for Tier 2 is that
platform maintainers are expected to take primary and long-term
responsibility for keeping the `main` branch and wheel builds
working. While none of us Pyodide maintainers (Hood Chatham, Gyeongjae
Choi, and I) is a NumPy maintainer at the time of writing, we are
committed to volunteering for said responsibility as platform experts,
in the same way as was discussed for our Android and iOS friends and
counterparts [3] earlier this month.
My belief is that the presence of pyemscripten wheels for NumPy on PyPI
will have long-reaching benefits overall:
- Up-to-date NumPy releases for Pyodide users: the current stable
Pyodide release, 314.0.8, ships NumPy 2.4.6, while the latest NumPy
release is 2.5.5. With wheels on PyPI, a new NumPy release can be
installed in Pyodide on the day it comes out, through micropip in the
browser or through `pip` in a Pyodide virtual environment, in the same
way as on any other platform. It will no longer have to wait for us to
update a recipe and make a Pyodide release.
- Packaging for Pyodide: we can get rid of a lot of code in the Pyodide
ecosystem, over time. This will be pretty useful in two places (and
counting): for micropip, Pyodide's in-browser package manager, to not
query a custom index to install NumPy. pyodide-build will not need to
include NumPy to be installed as part of its xbuildenv, nor will it
need to perform the current complicated steps to make it available
when compiling a project that depends on NumPy at build time, or, at
least, perform them at the same level of complexity. Out-of-tree
builds for our packages will thus be more straightforward and easier
for us to maintain.
- Interactive documentation: it will be far easier for NumPy to
integrate versioned WASM NumPy wheels as part of its interactive
documentation needs. Currently, the version of NumPy is coupled with
the version of the Pyodide kernel that JupyterLite ships, and it is
difficult to support a nightly pyemscripten wheel without jumping
through hoops, or to match it with the version of the NumPy
documentation that is being viewed, such that interactive examples for
NumPy 2.6 run a WASM build of NumPy 2.6.
A long-form proposal, with all the details, rationale, and
supporting information, including answers to common questions
that may arise, is in the GitHub issue noted above.
Thank you for your time!
Best,
Agriya
[1] https://pyodide.org/en/stable/
[2] https://numpy.org/neps/nep-0057-numpy-platform-support.html
[3]
https://mail.python.org/archives/list/[email protected]/thread/SQPBDNOJKMUPII2WUAQFD4P2NMB3Q54J/
_______________________________________________
NumPy-Discussion mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3//lists/numpy-discussion.python.org
Member address: [email protected]