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).
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