Joe Rickerby

I don't see a strong need for this, and since PEP517 we're increasingly in a world where this shouldn't be necessary. So, for now at least, I'm gonna close this...

Thanks for sharing your workaround @nicholasjng !

[Podman support](https://cibuildwheel.readthedocs.io/en/stable/options/#container-engine) was merged a year ago, so I think the motivation for the initial request of invoking cibuildwheel inside the container is gone. Podman is the solution for environments...

Being that GitHub Actions is now really the defacto preferred option for running cibuildwheel, I'm not so sure my previous objections hold so much weight. I'm gonna try publishing on...

Ack, not so simple. I'll have to contact support I think, I don't see an existing action with this name. [support ticket](https://support.github.com/ticket/personal/0/2199523)

update on the ticket... > Hi Joe, > > Thank you for writing to GitHub Support. > > I have opened an issue with Engineering to ask if the name...

> Hi Joe, > > Apologies for taking a while to get back to you on this. > > Engineering needs to make some additional updates before the name is...

> Hi Joe, > > Just gotten an update from Engineering that unfortunately that name cannot be currently released due to internal tooling of how the listings are registered, sorry....

This seems reasonable to me. I think I'd tack it onto #944, exposing them as envvars `$CIBUILDWHEEL_BUILD_TMPDIR` (a temp dir for a single build) and `$CIBUILDWHEEL_TMPDIR` (that exists for the...

Actually I just had another idea. You could accomplish it like this: ``` [tool.cibuildwheel.macos] before-all = [ "pip3 install conan", "conan profile new $ENVTMPDIR/conan/.conan/profiles/default --detect --force", "conan install ./ --build...