rye list: Never modify or delete the virtualenv #1351
Merged
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.
Previously, in some situations,
rye pin <pythonversion>; rye list
could lead to rye deleting the existing virtualenv.I suggest that
rye list
should be an interrogator and never modify any project. With this change, it lists its own and non-rye virtualenvs (same behaviour as uv pip freeze) but should never create, recreate or overwrite environments (own or non-rye).Fixes #1352