Henry Schreiner

> I'd probably make it a list of backends. We don't know what backend is being used, unless you mean just doing a textual match against the setting of `build-backend`...

I am still against any attempt to try to detect what backend is being used. It should be possible for someone to convert a build backend into a local build...

> Very few other backends utilize config settings This is heavily used in scikit-build-core and meson-python. I'd expect maturin might too - compiled backends are really likely to need configurable...

scikit-build-core supports cross compilation for macOS ARM and Pyodide. We also support it for Windows ARM with some small changes (compared to the minimal version) to your CMakeLists.txt. > I...

I think we are both hoping for some progress on the sysconfig proposal @FFY00 is working on. Generic cross-compilation is hard, especially if you need to support manylinux. Any further...

> You have different users, with different requirements, than pip, and this almost certainly translates to different trade-offs being appropriate. If build starts supporting custom prefixes for `--config-settings`, I think...

What I think would work would be a `--json-output=` (bike shedding fine) option that would write out the filename (and a bit more info if anything makes sense) to a...

When uv is building (like for `uv pip install` or the experimental build command (requires a dev build), it needs to communicate between processes. Stdout/stderr can't be used, so uv...

You can't reopen a PR that has been force pushed while closed. But you can make a new PR.

Also, I know one of the issues is that the special arches generally require newer compilers. The reason NumPy couldn't use manylinux_2_24 wan't due to C++ features (they didn't use...