Disabled package tracker for 0.28 release

[ryanking13]

Following packages are currently disabled in the main branch, which is a (soft) blocker for Pyodide 0.28 release. It is not mandatory to enable all the packages for the release (we can mention it in the release note and fix it later or ask others' help), but it would be nice to enable packages that are easy to fix.

This issue is to track the status of the disabled packages:

1. Requires maintainers to provide a wheel with new xbuildenv

• arro3-io (Request to update Pyodide build toolchain version kylebarron/arro3#343)
• arro3-compute
• arro3-core
• polars
  • has emscripten 4.0.9 build, but it should be recompiled with wasm-exception enabled.
• css-inline (Request to update Pyodide build toolchain version Stranger6667/css-inline#447), chore: Update recipe for css-inline #112
• pyarrow (Request to update Pyodide build toolchain version joemarshall/pyarrow-pyodide#5)
• osqp
  • it use CIBW, so probably CIBW should make a release including Add pyodide 0.28 pypa/cibuildwheel#2431?
• duckdb (Request to update Pyodide build toolchain version duckdb/duckdb-pyodide#7)

2. Lacks Python 3.13 support

• gensim: No 3.13 compatible release
• zarr - the latest release that supports 3.13 requires threading module – will be hopefully resolved with Add Pyodide support and CI jobs for Zarr zarr-developers/zarr-python#1903
• pygame-ce: the latest release that supports 3.13 changed the build backend to meson, but it does not support emscripten platform

3. Has build issue

• casadi: Re-enable CasADi #89
• clarabel
  • cvxpy-base (depends on clarabel)
• pyproj: signature mismatch
  • geopandas (depends on pyproj)
  • Cartopy (depends on pyproj)
• RobotRaconteur: No idea (fixed by maintainer: Fix RobotRaconteur with Emscripten 4.0.9 pyodide#5677)

---

My idea is to

1. enable all possible packages in [1] by asking maintainers to update the packages (we can probably give some deadline)
2. Enable casadi, pyproj, which I think is easy to fix.
   2.a) Personally, I would like to fix pygame as well, but it doesn't seem easy
3. Leave other packages disabled, make a release, and fix them later.

@hoodmane @agriyakhetarpal WDYT?

[agriyakhetarpal]

Your idea sounds good to me!

1. In the interest of time, I'll go ahead with CasADi, which we do have a stopgap solution for. We can take a look at the SUNDIALS_EXPORT issue later; I'll open an issue to keep track of it.
   2 Re: Zarr; the use of threading is also a reason why Add Pyodide support and CI jobs for Zarr zarr-developers/zarr-python#1903 was blocked back then, but on another look, I see that we should be able to set

   zarr.config.set({
       "threading.max_workers": 1,  # or None?
       "async.concurrency": 1,
   })

in order to restrict all IO operations that rely on multiple threads. Maybe that snippet can be added at init time and things would work? I'll also revisit my PR.
3. If gensim has no release supporting Python 3.13, we should leave it out, and if someone raises a request to add it back, we can do so with 0.28.x releases or when Python 3.13 support lands, whichever comes first – like you mentioned in point 3. It is already being discussed in piskvorky/gensim#3611, and I've spotted @hoodmane in piskvorky/gensim#3601 :D
4. For packages that require a new build with nightly xbuildenvs, I assume we've frozen our Emscripten updates with the 4.0.9 release, and we can ask them to use the one from 20th May, i.e., https://github.com/pyodide/pyodide-build-environment-nightly/releases/tag/20250520? If we have any more updates, another xbuildenv will come out with them tomorrow.
5. I think pygame-ce should be included if possible, as it took a reasonable time to support in the first place. However, I understand the necessities of the release timeline as well. Also, you did manage to fix pyxel in #98, so only one game engine is left. :)
6. Clarabel has had a new 0.11 release, maybe things are fixed now? https://github.com/oxfordcontrol/Clarabel.rs/releases/tag/v0.11.0

Also, should we tag the respective package maintainers here itself?

[ryanking13]

in order to restrict all IO operations that rely on multiple threads. Maybe that snippet can be added at init time and things would work?

Yeah, it would be worth checking if it works.

we can ask them to use the one from 20th May, i.e., https://github.com/pyodide/pyodide-build-environment-nightly/releases/tag/20250520? If we have any more updates, another xbuildenv will come out with them tomorrow.

It should be https://github.com/pyodide/pyodide-build-environment-nightly/releases/tag/20250523-emscripten_4.0.9. 20250520 contains Emscripten 4.0.8 (The GitHub releases UI sorts the releases strangely).

6. Clarabel has had a new 0.11 release, maybe things are fixed now?

Thanks for the info. Let's try.

[ryanking13]

5. I think pygame-ce should be included if possible, as it took a reasonable time to support in the first place. However, I understand the necessities of the release timeline as well. Also, you did manage to fix pyxel in Use emscripten 4.0.9 and enable pyxel #98, so ozly one game engine is left. :)

I tried it once, but it wasn't straightforward. Maybe we need some help from pygame maintainers.

Hi, @pmp-p, does pygbag support Python 3.13? I wonder if you managed to make pygame>=2.5.1 work in pygame-web.

[ryanking13]

Also, should we tag the respective package maintainers here itself?

Yeah, let me open an issue for each repository and mention them in this issue as well for visibility.

[agriyakhetarpal]

Ah yes, thanks for the link to the newer nightly!

I tried to build Clarabel 0.11, but it keeps failing with error: the option Z is only accepted on the nightly compiler despite the fact that I've set the nightly toolchains as default and I've the Rust sysroot based on our ABI docs. I'll try to debug that at a later point. In the meantime, I'll take a look at Zarr 3.