add CLI entry-point for uv #471
Open
Conversation
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.
Thinking about the future usage of this tool, I didn't like how you had to use the
-mflag to execute it as a module. So I added an entry point in our Python project managerUVto run it directly so that you can skip some words when calling the CLI.old way:
uv run python -m foonew way:
uv run fooalso updated docs, and added explanation how to run it from the repo root by using the flag
--project PythonScripts(idk though if that's really easier than picking up whatcddoes)next PR, I want to rename it to be consistently called
localization_tool, like discussed earlier