Henry Schreiner
Henry Schreiner
I'm curious to see if this fails CI. I know there's a bug which I've just fixed locally but would like to see if anything in CI catches it.
Okay, "no space left on device" wasn't the failure I was expecting...
@hoodmane, do you know why tests are failing to set up a venv? FWIW, I'm testing it locally with awkward-array like this: ```bash docker run -v $PWD:/cibuildwheel -v $PWD/../../scikit-hep/awkward:/awkward -w...
Ahh, yes, that's there in: https://github.com/scikit-hep/awkward/blob/2d259cc54e3787f1d285a57274e5ce5748ff110f/.github/workflows/docs.yml#L112 Not sure how I'm supposed to pass that with cibuildwheel, though.
@hoodmane would adding an environment variable version of `--exports whole_archive` be a good idea for 0.23.4?
That's a deprecated package, and doesn't help here anyway. And cibuildwheel does not read requirements from pyproject.toml. Having a way to get cibuildwheel to continue on error and list the...
> It sometimes fails for testing You can use `PIP_ONLY_BINARY: numpy`, etc. One reason it's good to do this per-package. > But waiting on error may be a waste of...
(https://github.com/pypa/cibuildwheel/issues/1062)
It wouldn’t help I think, we need https://github.com/pypa/manylinux/pull/1564 and that’s blocked awaiting on the pip release. (We also need macOS binaries for free threading that are planned for beta 2)...
So, while waiting for binaries, how are we going to support this? A new identifier? Opt in or opt-out?