Henry Schreiner
Henry Schreiner
I think this is the remaining bug: https://github.com/pypy/pypy/issues/4958 I'm not sure how to go about patching it for now though. I think if tox normalized the path on Windows, that...
For compiled use case (like scikit-build-core and meson-python), it's the build venv.
I think there are two ways. The most flexible is to add [a custom backend](https://setuptools.pypa.io/en/latest/build_meta.html#dynamic-build-dependencies-and-other-build-meta-tweaks), and process them there. This would allow any form of config setting, and not just...
Not directly an answer, but can you use `virtualenv` instead of `venv`? That should have a recent version of pip, I think?
I’ve already dropped 4 and 5 locally. :)
We need to fix the tests for pytest 7.4+, as I think pytest 8 is required on Windows with 3.13.
See https://learn.scientific-python.org/development/guides/packaging-compiled/. This should all work just fine with uv, AFAICT any valid PEP 621 backend should work, which is all of them except Poetry (and that's currently a WIP...
Setuptools also doesn't support multithreaded builds, IDEs, limited cross-compile support, no common things like C++ standard, no support for other libraries like Boost, etc. You basically get a bare-bones compile...
The biggest issue is I don't think output is shown by default except for `uv build`. So a compiled backend will sit for minutes showing nothing.
You can do `uv init --lib --build-backend scikit` (or `setuptools`, but there you'd have to manually set up the extensions) to get started.