feat(dev): commit uv.lock; make uv sync the canonical dev setup#86
Merged
Conversation
Adopt uv as the canonical developer workflow. The maintainer's dev loop is `git clone` + `uv sync` + `uv run`, with `git pull` + `uv run` to update. - Commit uv.lock (134 packages, resolved for Python 3.11) so every developer and CI run gets the exact pinned dependency set, including orjson==3.11.8. - README, docs/USER_GUIDE.md, CONTRIBUTING.md: make `uv sync` / `uv run` the canonical source setup; demote the plain-venv path to an alternative. Keep the Python 3.11 statement up front (uv reads the pin itself). - docs/DEV_UV.md: reframe uv as canonical (conda now the parallel option); document `uv lock --upgrade` as the maintainer dep-bump flow and note the lock is committed / applied with --frozen in CI. - CI (test.yml): install via astral-sh/setup-uv + `uv sync --frozen` and run pytest under `uv run --frozen`, for reproducibility against uv.lock. .venv/ was already git-ignored; uv.lock is not ignored. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
dustenhubbard
enabled auto-merge (squash)
July 21, 2026 21:56
dustenhubbard
added a commit
that referenced
this pull request
Jul 23, 2026
Adopt uv as the canonical developer workflow. The maintainer's dev loop is `git clone` + `uv sync` + `uv run`, with `git pull` + `uv run` to update. - Commit uv.lock (134 packages, resolved for Python 3.11) so every developer and CI run gets the exact pinned dependency set, including orjson==3.11.8. - README, docs/USER_GUIDE.md, CONTRIBUTING.md: make `uv sync` / `uv run` the canonical source setup; demote the plain-venv path to an alternative. Keep the Python 3.11 statement up front (uv reads the pin itself). - docs/DEV_UV.md: reframe uv as canonical (conda now the parallel option); document `uv lock --upgrade` as the maintainer dep-bump flow and note the lock is committed / applied with --frozen in CI. - CI (test.yml): install via astral-sh/setup-uv + `uv sync --frozen` and run pytest under `uv run --frozen`, for reproducibility against uv.lock. .venv/ was already git-ignored; uv.lock is not ignored.
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.
Maintainer decision: uv is the canonical dev environment.
uv.lockcommitted (134 packages, requires-python ==3.11.*, cross-platform markers; orjson pin honored; only non-registry sources are the intended funlib git dep and the project itself as editable).git clone->uv sync->uv run PyReconstruct; update loop isgit pull+uv run. Plain venv demoted to a details block;uv lock --upgradedocumented as the dep-bump flow.uv sync --frozen— reproducible against the lock, no pip/setup-python.Validated end-to-end: suite 1232 passed, 5 pre-existing xfails, executed via
uv run --frozen(~12 s). (This PR's own CI run doubles as live validation of the new workflow.)🤖 Generated with Claude Code