Upload emscripten wheels to PyPI

[oscarbenjamin]

@agriyakhetarpal now that PEP 783 for emscripten packaging is accepted does that mean that we can upload the pyodide wheels straight to PyPI?

I think that implementing this would just be a case of removing the rm line here and then making a new release:

python-flint/.github/workflows/buildwheel.yml

Lines 479 to 497 in d521145

	# Downloads all artifacts
	- name: Download release artifacts
	uses: actions/download-artifact@3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c # v8.0.1
	with:
	path: wheelhouse
	merge-multiple: true
	- name: Copy the PyPI files into dist
	# pyodide wheels cannot be uploaded to PyPI
	run: |
	mkdir dist
	rm wheelhouse/*pyodide*.whl
	cp wheelhouse/*.whl wheelhouse/*.tar.gz dist
	- name: Publish package on PyPI
	# It is recommended to pin a commit hash here for security but it
	# should be kept up to date. Possibly all actions and dependencies used
	# by the build script should be pinned...
	uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # v1.14.0

[agriyakhetarpal]

Hi @oscarbenjamin, yes, we can! The pyemscripten_2025_0 (2025 ABI) wheels with Pyodide 0.29.4 are all fine to release to PyPI, but I would suggest waiting around a ~week or so to upload wheels for the 2026 ABI, as the Pyodide 314.0.0 stable release is not out yet – we only have alphas for it (see pyodide/pyodide#6233).

[agriyakhetarpal]

Pyodide 314.0.0 stable is out: https://blog.pyodide.org/posts/314-release, so you should be unblocked to release now. Note that cibuildwheel is being updated (pypa/cibuildwheel#2906 was merged, but it needs a v4.1.0 release, which I'm coordinating on), but we haven't changed anything ABI-related between 314.0.0a2 and 314.0.0 final as such. So you can release with cibuildwheel right now if you'd like, or wait a bit, or you could use pyodide-build manually outside of cibuildwheel which will grab the 314.0.0 stable xbuildenv by default. Thanks!

[agriyakhetarpal]

cibuildwheel v4.1 is out: https://github.com/pypa/cibuildwheel/releases/tag/v4.1.0

[oscarbenjamin]

I guess new pyodide means that this should be updated as well:

python-flint/.github/workflows/buildwheel.yml

Lines 13 to 18 in 870524f

	# These four values need to be kept in sync. Each pyodide version pins an
	# emscripten version and a CPython version.
	PYODIDE_VERSION: '0.29.3'
	PYODIDE_EMSCRIPTEN_VERSION: '4.0.9'
	PYODIDE_PYTHON_VERSION: '3.13'
	PYODIDE_CIBW_BUILD: 'cp313-*'

[oscarbenjamin]

I've opened a PR gh-401

[oscarbenjamin]

I've merged gh-401 but a new release would be needed to actually upload the wheels to PyPI.

[agriyakhetarpal]

Thank you! I noticed a few things there that are now redundant – let me open a follow-up PR for that.

[agriyakhetarpal]

Never mind; those should be kept because the UX for building libraries isn't as nice in cibuildwheel's before-all step. Sorry for the noise!

[oscarbenjamin]

Thanks for looking!

I think we are almost there. Please do let me know if you spot anything problematic because I plan release/upload soon (this week).

In gh-401 I removed the patching of emscripten because the patches didn't apply any more. Hopefully they are just not needed now (I don't know if they were needed before either...).

[agriyakhetarpal]

I think we should keep the patching IMO, just that you might need to bring them for https://github.com/pyodide/pyodide/tree/314.0.0/emsdk/patches which apply to Emscripten 5.0.3. So I might have been wrong. Let me look again more closely, on my computer this time instead of on my phone...