jupyterlite/pyscript/pyodide wheel compatibility?

[AndrewAnnex]

I am experimenting with building pyodide wheels for my c/cython python extension and managed to get something that seems to work.

I was wondering what the compatibility story was with jupyterlite and supporting pip installs of the wheels with it, but for jupyterlite ran into an issue where the wheel name didn't match the expected "emscripten_3_1_58_wasm32" name for when I got to https://jupyter.org/try-jupyter/lab/ while cibuildwheel was producing "pyodide_2025_0". I was also building a python3.13 wheel versus the necessary 3.12 one, but that I know how to address.

I am guessing that I should mess around with the versions listed in pyodide xbuildenv search --all, but a cursory read of https://cibuildwheel.pypa.io/en/stable/platforms/#pyodide-choosing-a-version didn't quite have the higher level specific info on how to ensure properly compatible wheel names are made.

Just looking for any info, I'd be happy to contribute some docs on this topic eventually

[AndrewAnnex]

okay I have answered some of these questions for myself regarding compatibilities but not the issue of the wheel names totally, I fixed my pyodide version to 0.27.7, but I can see that repair wheel is renaming the wheels:

 *** Making wheel...
  2025-08-22 15:39:53,989 - scikit_build_core - INFO - Discovered Python package at src/test_cyice
  *** Created test_cyice-0.0.1-cp312-cp312-emscripten_3_1_58_wasm32.whl
  Unpacking to: /tmp/tmpndij7kee/test_cyice-0.0.1...OK
  Repacking wheel as /tmp/cibw-run-48phdy5r/cp312-pyodide_wasm32/built_wheel/test_cyice-0.0.1-cp312-cp312-pyodide_2024_0_wasm32.whl...OK
  Successfully built /tmp/cibw-run-48phdy5r/cp312-pyodide_wasm32/built_wheel/test_cyice-0.0.1-cp312-cp312-emscripten_3_1_58_wasm32.whl
                                                            ✓ 199.23s
Testing wheel...
  
  + Download https://nodejs.org/dist/v22.17.1/node-v22.17.1-linux-x64.tar.xz to /tmp/tmpzz_mi2dk/node-v22.17.1-linux-x64.tar.xz
  + pyodide venv /tmp/cibw-run-48phdy5r/cp312-pyodide_wasm32/venv-test
  Creating Pyodide virtualenv at                                                  
  /tmp/cibw-run-48phdy5r/cp312-pyodide_wasm32/venv-test                           
  ... Configuring virtualenv                                                      
  ... Installing standard library                                                 
  Successfully created Pyodide virtual environment!                               
  + which python
  /tmp/cibw-run-48phdy5r/cp312-pyodide_wasm32/venv-test/bin/python
  + pip install /tmp/cibw-run-48phdy5r/cp312-pyodide_wasm32/repaired_wheel/test_cyice-0.0.1-cp312-cp312-pyodide_2024_0_wasm32.whl
  Looking in indexes: https://pypi.org/simple, file:///home/runner/.cache/cibuildwheel/pyodide-build-0.30.5/0.27.7/xbuildenv/pyodide-

This renaming I think is fine, but I am not sure why I was having issues with micropip. Or rather, why micropip was expecting a different tag.

[AndrewAnnex]

after more work, I think I've got this fully resolved more myself, in that the docs are accurate that pyodide xbuildenv search --all did provide some information but I ultimately got a complete answer from the README at https://github.com/jupyterlite/pyodide-kernel . I think it could be useful to add a similar table to the docs here, or to reference pyodide-kernel as well