Joe Rickerby

I _nearly_ considered using a template as the 'minimal config' in cibuildwheel, but I decided in the end that it's better to spell it out natively, so there isn't a...

> 1. The manylinux builder seems to copy the project directory rather than just mounting it. On some CIs, (I know Circle, not sure about the others), mounting doesn't work...

Thanks for the debugging. We could use a better error message for this then. @mayeut I'm guessing manylinux1 also won't get Python 3.11?

Yep, it is detected, it's just the error message is confusing because that message is assuming that the user has fiddled with PATH to break it, not that it never...

> The `/opt/python/cp38-cp38/bin/python` python mentioned is the one used as a build driver inside the container (counterpart to the host python running cibuildwheel). I don't recall adding this to PATH...

ahh.. gotcha. So the cp38 in PATH thing really is a red herring. It's only a result of trying to investigate this using before-all.

Hmm. I'm thinking more about this and I wonder if perhaps `--build` should override both CIBW_BUILD and CIBW_SKIP from environment/config. There seems something weird about the user doing explicitly `cibuildwheel...

Ah, in fact the issue might be deeper than that, for development machine use. [This comment](https://github.com/pypa/cibuildwheel/issues/1087#issuecomment-1097325078) raises another potential confusion, which is that `cibuildwheel --build 'pp38-manylinux_x86_64'` wouldn't even work at...

`--only` makes sense to me!

I've just pushed a few commits. After removing the `intercepted_build_args` to `platform` coupling, I realised that CIBW_PLATFORM was causing an error when used with the `--only` command line option, which...