So @henryiii do you have any suggestions of how we can start working this? Thanks to @hoodmane work out-of-tree builds are starting to looks reasonably good (example in numpy/numpy#21895 where the test runner is also going to be shipped by Pyodide soon). So how do we move forward on this?

From what I can tell for simple packages, right now the constraints are,

at least in the numpy CI the build seems to be fine in GHA with ubuntu-latest, but I wonder whether it wouldn't be better to build in the pyodide-env Docker container anyway, similarly to manylinux.
running tests is still a bit WIP so there should be a way to disable it just for this build (particularly, that there is bound to be some tests that need fixing for WASM)
whatever we do, it should still be a somewhat experimental opt-in feature and not enabled by default.
and also we still have nowhere to upload the produced wheels Better wheel hosting solution pyodide/pyodide#3049 short of storing them as CI artifacts

Should we try to make it work with just 1 CI provider to start: say GH Actions?

Pyodide Wheels #1002

Description

Description

Build log

CI config

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions