Joe Rickerby

Well, yes, it is kinda tempting. In fact, [I already did it once](https://github.com/joerick/cibuildwheel/blob/461aa35f99f82d8e762c9d77379c4fdc04d69a69/cibuildwheel/linux.py) in #458, but rolled it back when I decided not to use context managers for the logging....

If you are building using your own script, you'll have to ensure that you're building the correct arch. The easiest way to do this in before-build is to look at...

All Github actions runners are x86_64 for macos, so we cross-compile to universal2 and arm64.

This announcement is for self-hosted runners, meaning you can now run Github Actions on your own M1 hardware. But most people will be waiting for Github-hosted arm64 runners.

Aside: CI is flaky at the moment. Seems to be an intermittent issue with PyPI, I've been seeing lots of errors like > WARNING: Skipping page https://pypi.org/simple/filelock/ because the GET...

So far I've decided not to do this, because once a project is published, Github shows a banner like this on the repo:  The language here is a bit...

Yes, that makes sense to me. I think that originally it was `nosetests` in the testing tests rather than pytest so that we were sure that TEST_REQUIRES had worked. So...

We have seen this exception a few times before in cibuildwheel on Windows, sometimes in pip, sometimes when we're cleaning up a test venv. Is this error persistent - does...

The idea has been mooted a few times! But generally we find other ways around the problem that don't require modifying the actual build. The actual build invocation seems pretty...

Maybe I'm missing something, but what is the use-case for such a feature? As henryiii mentioned, the specific Python binaries used are quite important, so you'd probably end up needing...