Henry Schreiner

Keep in mind, manylinux will not support this, as it does not have virtualenv installed, and it does not touch the "base" python, so you need to be using one...

> Ignore cibuildwheel, which is unusable in some environments that can't use those CI environments it supports Final quick comment, not related to the discussion here but addressing the comment...

There actually is a general place for "tools", pyproject-build could go there, actually. It might not a good idea, because you want to build with specific interpreters, and not accidentally...

> Against what I asked, you keep dragging back manylinux into this discussion No, you asked not to talk about cibuildwheel. I fully understand that there are places to use...

PS: my favorite name for this would be `--virtualenv`, as that makes it very clear it requires virtualenv to work. It's the virtualenv target python. Otherwise we will get a...

I am perfectly aware you can split a string with a comma. I am also aware that a comma is a perfectly valid character in a filename on some systems...

`python -m build wheel-python 3.7 --wheel-python 3.8 .` is not that much better than `python -m build wheel-python 3.7 . && python -m build --wheel-python 3.8 .`, while the later...

Using `os.pathsep` would also not be cross-platform, by the way. I'd actually just make it multiple calls rather than anding them together: ```python python -m build --sdist python -m build...

Being able to target a different Python may be useful for the SDist in some cases: #269 for example.

On what system and with what pip options? Build should be building in a dedicated temporary environment and getting the PyPA package for CMake. Which should work.