chore: migrate Python deps from requirements-lock.txt to uv lock#21
Open
CameronBrooks11 wants to merge 2 commits into
Open
chore: migrate Python deps from requirements-lock.txt to uv lock#21CameronBrooks11 wants to merge 2 commits into
CameronBrooks11 wants to merge 2 commits into
Conversation
Replace the manual pip freeze workflow with uv's native lock file: - Add [project] + [project.optional-dependencies] dev to pyproject.toml - Generate uv.lock (resolver-guaranteed consistency) - Update all CI workflows to use astral-sh/setup-uv + uv sync --locked - Remove requirements.txt and requirements-lock.txt - Update renovate.json: pep621 manager, lockFileMaintenance, ignore legacy files Renovate now manages deps via the pep621 manager and will run lockFileMaintenance weekly to keep uv.lock current.
CMake's find_package(Python3) must discover the venv Python (which has pytest installed), not the bare system Python. Prefixing cmake configure with 'uv run' puts .venv/bin first on PATH so CMake stores the correct Python3_EXECUTABLE. CTest then invokes the venv Python which has all packages available.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces the manual
pip freeze > requirements-lock.txtworkflow with uv's native lock file (uv.lock).Changes
[project]section with[project.optional-dependencies] devdeclaring all Python deps (previously inrequirements.txt)uv lock— resolver-guaranteed consistent resolutionpip install -r requirements-lock.txttoastral-sh/setup-uv+uv sync --locked --extra devrequirements.txt,requirements-lock.txt, lockfile validation stepspep621manager, enabledlockFileMaintenance(weekly), ignored legacy filesWhy
The old pattern (
requirements.txtranges +requirements-lock.txtpins) had no automated way to keep the lock file in sync. Renovate'spip_requirementsmanager bumps individual pins without resolver guarantees, creating noise and potential inconsistency.With
uv lock:pep621manager natively understandsuv.locklockFileMaintenanceregenerates the full lock weeklyanolis-workbenchLocal dev