Repository navigation
fix(cli)!: keep the invoked Python environment - #18
Merged
Merged
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.
Keep Rattle in the invoked Python environment instead of switching to a project-local executable. Rule-import errors identify missing modules or dependencies and the active interpreter.
Breaking Changes
Select the Python environment containing Rattle and its custom-rule dependencies explicitly. In a uv project that declares those dependencies, run:
uv run python -m rattle check .The same environment requirement applies to editor integrations and pre-commit hooks.
Verification
just test -- -qexercises interpreter selection and rule-import failures on Python 3.11 through 3.15uv run python -m rattle check .reports a rule violation from a scratch project's installed Rattle