Henry Schreiner

Okay, I'lll try to help fix this soon. I can try running that locally, then figuring out what is different.

Looks like just the editable install is failing (at least on the one that has finished so far) :) I've fixed the actions so it should run when you make...

Curious, it seems to be that Windows passes the non-editable install check, but Linux does not. Are you on Windows too?

All workflows fail, because the editable install fails. I'm mostly looking at the non-editable install, which I'd expect to work. It seems to work on Windows, but not Linux. This...

I'll try to help soon-ish, but https://scikit-hep.org/developer/pytest#running-pytest describes how to debug with pytest. You can use `--trace` to start a debugger at the beginning, or `--pdb` to start the debugger...

The regular install works with/without, and the editable install does not work with or without the patch. :(

See https://github.com/scikit-build/scikit-build/issues/594#issuecomment-949901215 You should be able to pass things through to CMake via CMAKE_CONFIGURE_OPTIONS envvar.

It is in #606. I don't like the name SKBUILD_CONFIGURE_OPTIONS, because it doesn't match `cmake_args=`, I'd rather `SKBUILD_CMAKE_ARGS`. It's not too bad, you'll go from: ```bash python setup.py install --build-type...

Plus, if you use `pyproject.toml`, you'll no longer need to worry about scikit-build or anything else being pre-installed, as `pip` or `build` can install things in pyproject.toml, while `python setup.py`...

I'm very much working on making this all go away, see scikit-build-core. The idea is to have a pure PEP 517 builder for projects with little Python, and backends (including...