Henry Schreiner

Scikit-build-core (and I think Maturin) only uses the `ARCHFLAGS`, since it would be a bug to set `_PYTHON_HOST_PLATFORM` and `ARCHFLAGS` differently. Most other tools use `ARCHFLAGS` to control the target...

`pybind11-global` installs into the data directory of the wheel (`/include` and `/share`, IIRC). That produces "nice" linux-style structure. It's also surprising / dangerous to write to your root if you...

You can also just put an commit SHA here. But yes, pre-commit caches assuming the `rev` will never change, so you should never use `master`/`main`.

PyLint's handling of this is much better, FWIW. I don't think I've ever had a false positive from PyLint's else after control flow checks.

You don’t need else after a control flow statement. That’s `return`, `yield`, `break`, or `continue`. Remove the “el” in front of the elif.

Closed by https://github.com/charliermarsh/ruff/pull/2615 ?

Also very useful for pyenv, where you may want to run `(pyenv prefix 3.7.8)/bin/python` for example.

A build backend should not put anything into the source directory by default. It's perfectly valid to have two virtual environments, with two different Python versions, running from one source...

FYI, here are my stub files for boost-histogram: https://github.com/scikit-hep/boost-histogram/tree/develop/src/boost_histogram/_core - they describe `boost_histogram._core`, the shared lib. Based on an initial run with `stubgen` then lots of manual updates because pybind11...

> Might these changes yield a solution? I'm not sure, but the improved version is a WIP at https://github.com/scikit-build/scikit-build-core/pull/399. Mixing an source directory and an installed directory is rather new...