Bootstrap unmanaged uv installation #1742
Merged
Conversation
This file contains 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
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.
I noticed that
uv self updatewill fail if there are multiple self-updating-capable uv installations on a system.Typically, if a
uvis already installed, reticulate will use that. reticulate only bootstraps a uv installation into its cache dir ifuvis not found.However, before this PR, if user installs uv manually after reticulate has bootstraped an installation, then
self updatewill later error with:This is because the self-updater checks the
.config/uv/uv-receipt.json, which is written to by install scripts unless self-updating is disabled.This PR switches to bootstrapping the installation with
UV_UNMANAGED_INSTALLset.