Conversation
Without a [build-system] table, uv treats the project as unpackaged and skips installing the patchwork CLI entry point. Add hatchling as the build backend so uv sync installs the command correctly.
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.
What
Fix the
patchworkCLI command not being installed byuv sync. Without a[build-system]table inpyproject.toml, uv treats the project as unpackaged and skips entry point installation, causinguv run patchworkto fail with "No such file or directory".How
pyproject.toml— Add[build-system]table withhatchlingas the build backend. This tells uv to build and install the package (including thepatchworkCLI entry point) into the virtual environment.uv.lock— Updated automatically; source changes fromvirtualtoeditable.Recommended Review Order
pyproject.toml