I would like to add a uv install path in parallel to the existing pip support, so developers who prefer modern Python packaging have that option. The current pip/conda flow stays untouched.
If this is in line with the project's direction, I'd like to put up a PR for it.
One preference for the PR: I'd lean toward Hatchling over setuptools as the build backend. It's pyproject.toml-only, supports uv.lock for reproducible envs, and removes the need for the --use-pep517 / --no-dependencies flags currently used.
I would like to add a
uvinstall path in parallel to the existing pip support, so developers who prefer modern Python packaging have that option. The current pip/conda flow stays untouched.If this is in line with the project's direction, I'd like to put up a PR for it.
One preference for the PR: I'd lean toward Hatchling over setuptools as the build backend. It's pyproject.toml-only, supports
uv.lockfor reproducible envs, and removes the need for the--use-pep517/--no-dependenciesflags currently used.