Adopt uv for the dev environment - #65
Merged
Merged
Conversation
- Move package metadata from setup.py to PEP 621 pyproject.toml with hatchling; version still read from version.md so bump-version keeps working - Move dev dependencies to the uv dev dependency group; commit uv.lock - Delegate Makefile targets to uv; install-dev drops legacy egg-info that would shadow the uv-managed editable install - CI uses astral-sh/setup-uv and uv sync --locked; run-tests now also builds the package and checks wheel contents before a release can - Document the uv flow in README and TESTING.md
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
2 participants
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
Contributors' venvs could silently drift from the checkout: a stray
pip install snowcapreplaced the editable install with a PyPI release (observed: venv at 1.0.17 while source was at 1.0.23). This adopts uv souv syncgives a one-command dev setup that reinstalls the project editable and keeps dependencies pinned on every run.Closes #64
Changes
setup.pyto PEP 621pyproject.tomlwith hatchling; version still read fromversion.md, so the bump-version workflow keeps working unchanged[dependency-groups] devgroup; commituv.locksetup.py,MANIFEST.in,requirements.txt,requirements.dev.txtinstall-devdrops legacy*.egg-infothat would shadow the uv-managed editable installrun-tests,release-package,reset-test-account) usesastral-sh/setup-uv+uv sync --locked; run-tests now also builds the package and checks wheel contents (entry point, templates,py.typed) sincerelease-packageuploads straight to PyPIVerification
uv sync: snowcap 1.0.23 installed editable;snowcap --versionreports 1.0.23uv build+twine checkpass; wheel contains templates,py.typed, console entry pointmake lint,make typecheckclean; 2048 unit tests pass