You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Replace pip and uv pip in the dev tooling with uv-native commands #124
The dev tooling still installs with pip in several places: python -m pip install for bandit and pip-audit in test-jvm.yml, uv pip install --system for the wheel, the test dependencies and the build tools (test-jvm.yml, test-python-examples.yml, scripts/Dockerfile.build), uv pip compile in the dependency floor audit, python -m pip install inside the manylinux containers (test-jvm.yml, test-native.yml), uvx pip download in scripts/after_tag_verify.sh, uv pip install in scripts/ensure-build-tools.sh and scripts/build-native.sh, and uv venv plus uv pip install --reinstall-package in CLAUDE.md and the build.sh hint. Installing into the runner's Python with --system also lets one step leak packages into the next.
Proposed: use uv-native commands only. One-off tools run as uvx tool==X (same pins as today, build pinned at its latest release), wheel tests run as uv run --no-project --with "<wheel>[test]" python -m pytest, the example dependencies go into a uv sync project of their own, the floor audit resolves with uv lock on a throwaway project instead of uv pip compile, and every astral.sh/uv/install.sh URL pins the uv version. pyproject.toml stays a non-uv package definition (managed = false); converting it to a uv project is a separate decision.
Activity
Replace pip and uv pip in the dev tooling with uv-native commands (#124…