Repository navigation
[CHORE] manage the project with uv and a committed lockfile - #7
Merged
Merged
Conversation
Installs resolved whatever versions were current that day, so two people could not be sure they ran the same stack. The lockfile pins it, and .python-version lets uv fetch a matching interpreter for anyone. Dev tools move to a dependency group so they stay out of the published package. The cpu extra routes torch to the CPU-only index for machines that would otherwise download the CUDA runtime for nothing; the gpu extra exists because uv only locks both builds when two extras are declared as conflicting.
CI now tests exactly the locked versions, and --locked fails the build when pyproject changes without a re-lock. --no-sync keeps uv run from swapping the CPU torch back for the default build or switching away from the matrix's Python.
youssefassis
force-pushed
the
chore/uv-project
branch
from
October 5, 2026 13:21
a336464 to
cd54301
Compare
youssefassis
enabled auto-merge (rebase)
October 5, 2026 13:24
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.
Why
Installs resolved whatever versions were current that day, so two people could not be sure they ran the same stack. Now setup is one command (
uv sync) and everyone gets the locked versions.Changes
uv.lockcommitted,.python-versionset to 3.12 (uv fetches it automatically).[dependency-groups], souv syncinstalls them without flags and they stay out of the published package.classify-justifyconsole script;python -m classify_justifystill works.cpuextra routes torch to the CPU-only index. Thegpuextra mirrors the default build: uv only locks both builds when two extras are declared as conflicting.uv sync --locked --extra cpu, thenuv run --no-syncso the CPU torch and the matrix Python are kept.uvecosystem.Notes
--extra cpuon bothuv syncanduv run; a plainuv runwould re-sync to the default (CUDA) torch.Testing
uv run ruff check .clean,uv run pytest141 passed (Python 3.12, macOS).