Henry Schreiner

We stopped injecting setuptools and wheel in every environment in 2.18. If you add setuptools and wheel to the before-build libraries, it works. https://github.com/henryiii/pyomo/actions/runs/11865436281 I guess pip makes an isolated...

You could remove your `.coveragerc` file and place the config in pyproject.toml. You could also get rid of setup.cfg[^1]; I always configure pytest from pyproject.toml too. Ruff and uv can...

Can't you set `PIP_NO_BINARY=pysam`? Something like: ```toml [tool.cibw.linux.environment] PIP_NO_BINARY = "pysam" ``` Or is that not what you meant?

I think you could provide a wheelhouse, similar to PyPI, but with the Pyodide wheels built from the "in-tree" set of packages. That would provide some benefits even if upstreams...

Let us know if you need (the rest of) CI triggered. :)

python-build-standalone is fine, in fact, I'd like to use that for pyodide in the future, too.

Not following closely yet, but we do have python-build-standalone support now if you need a specific host Python. (Added for pyodide).

What about the linux arm runners on GHA? I’m a little surprised that is not an option here. From what I gather looking at this earlier, that means you can’t...

That's the worst I've seen copilot do, but the very first one is interesting, looking at `git grep ANDROID_API_LEVEL`, I see ``` cibuildwheel/resources/_cross_venv.py:53: api_level = sysconfig.get_config_var("ANDROID_API_LEVEL") ``` Which does look...

``` cibuildwheel/util/helpers.py:1:0: R0401: Cyclic import (cibuildwheel.platforms -> cibuildwheel.platforms.android) (cyclic-import) ``` Don't know why pylint is complaining about that. It's not even imported in that file. I fixed the other lints.