Warn when uv python upgrade tries to install over a non-managed bin installation#14084
Merged
jtfmumm merged 2 commits intofeature/transparent-python-upgradesfrom Jun 18, 2025
Merged
Conversation
Member
|
Should we hint / require Shouldn't |
jtfmumm
force-pushed
the
feature/transparent-python-upgrades
branch
2 times, most recently
from
eaaba7e to
f9f83c6
Compare
jtfmumm
added
the
enhancement
jtfmumm
force-pushed
the
jtfm/restore-force-to-upgrade
branch
2 times, most recently
from
732b57f to
b595b64
Compare
jtfmumm
force-pushed
the
jtfm/restore-force-to-upgrade
branch
from
b595b64 to
2cc1237
Compare
jtfmumm
changed the title
--force option for uv python upgradeuv python upgrade tries to install over a non-managed bin installation
Contributor
Author
I ended up removing the I've updated the PR title and description. |
zanieb
approved these changes
Jun 18, 2025
jtfmumm
merged commit 3dc1eb2
into
feature/transparent-python-upgrades
86 checks passed
jtfmumm
added a commit
that referenced
this pull request
Jun 18, 2025
…n` installation (#14084) `uv python upgrade` had originally had a `--force` option, but we thought it probably didn't make sense. However, switching `uv python upgrade` behind the preview flag revealed a bad interaction: upgrading a minor version when a non-managed interpreter of that version exists in the `bin` directory displays an error recommending the use of `--force`. This PR only warns if this case arises with `uv python upgrade`, noting that install `--force` can be used. It also includes a test for the case described above.
jtfmumm
added a commit
that referenced
this pull request
Jun 20, 2025
…n` installation (#14084) `uv python upgrade` had originally had a `--force` option, but we thought it probably didn't make sense. However, switching `uv python upgrade` behind the preview flag revealed a bad interaction: upgrading a minor version when a non-managed interpreter of that version exists in the `bin` directory displays an error recommending the use of `--force`. This PR only warns if this case arises with `uv python upgrade`, noting that install `--force` can be used. It also includes a test for the case described above.
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
2 participants
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.
uv python upgradehad originally had a--forceoption, but we thought it probably didn't make sense. However, switchinguv python upgradebehind the preview flag revealed a bad interaction: upgrading a minor version when a non-managed interpreter of that version exists in thebindirectory displays an error recommending the use of--force.This PR only warns if this case arises with
uv python upgrade, noting that install--forcecan be used. It also includes a test for the case described above.