Henry Schreiner
Henry Schreiner
> because it does exactly that for you ... whether they are downloaded or built locally That's the problem, it does not store wheels that are downloaded. So if you...
I’ll investigate, maybe it changed or there’s an another reason it was behaving like that.
The current directory should not be present unless the build backend adds it. `setuptools.build_meta` does not, while `setuptools.build_meta.__legacy__` does. I believe you can't stop Python from adding the current directory...
If you run “pytest”, then the current directory is not added to the path. But if you run `python -m pytest`, it is there (added by Python). You can try...
This is an extremely rare issue for building packages, since most tools would expect to install “logging” as a top level package, which would clash with the std lib. A...
FYI, `python -m venv .venv` doesn't work in the directory either, due to Python putting it at the top of the PATH. This means `pipx run` can't be used in...
Easiest way to fix this actually is to run `python -Im build`.
FYI, a good example of supporting this, without requiring CMake when building Cython, is at https://github.com/wjakob/nanobind/blob/master/cmake/nanobind-config.cmake (and an example that does require CMake at build time can be found in...
> How does the nanobind example avoid CMake? I might not have been clear - what I meant is `nanobind` itself doesn't use CMake to make SDists and wheels of...
On flight to SciPy, so might be a bit delayed looking at this. If anyone is at SciPy we can discuss there a bit.