Summary
The project already has a uv.lock file and uses uv sync in the CI type-check job, but tox.ini, CONTRIBUTING.md, and most CI jobs still use raw pip install. Adopting uv consistently across the project would speed up CI (faster dependency resolution and installs) and simplify developer setup.
Proposed changes
- CI: Replace
pip install invocations with uv across all CI workflow jobs
- CONTRIBUTING.md: Update developer setup instructions to use
uv
- tox: Potentially replace tox with uv-based test running
- scikit-build-core already supports uv, so the build backend is ready
Motivation
uv is significantly faster than pip for dependency resolution and installation. Since part of the infrastructure already uses it (the lock file and type-check job), completing the migration would make CI faster and reduce the number of package management tools contributors need to be familiar with.
Summary
The project already has a
uv.lockfile and usesuv syncin the CI type-check job, buttox.ini,CONTRIBUTING.md, and most CI jobs still use rawpip install. Adopting uv consistently across the project would speed up CI (faster dependency resolution and installs) and simplify developer setup.Proposed changes
pip installinvocations withuvacross all CI workflow jobsuvMotivation
uv is significantly faster than pip for dependency resolution and installation. Since part of the infrastructure already uses it (the lock file and type-check job), completing the migration would make CI faster and reduce the number of package management tools contributors need to be familiar with.