Use lockless uv workflow for pure Python - #167
Draft
timkpaine wants to merge 1 commit into
Draft
Conversation
Signed-off-by: Tim Paine <3105306+timkpaine@users.noreply.github.com>
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
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.
Pilots an end-to-end
uvworkflow in the pure Python template without committing a Python lockfile.developextra to the PEP 735devdependency group.uv pip, preserving fresh resolution of compatible package versions and editable ecosystem workflows without generatinguv.lock.uv buildfor isolated sdist and wheel creation, then checks those artifacts withcheck-dist.build, Hatchling, Twine,uv, andwheeldevelopment dependencies and updates generated documentation.Rendered the pure template with Copier under Python 3.12 and ran
make develop,make lint,make checks,make test, andmake dist. All passed, and nouv.lockwas created.