Merged
Conversation
Member
|
i suspect best in this case is to advise users to have a python already installed via conda/mamba or micros in this way they avoid the issue. |
Member
Author
Why not let uv install it for you? One less thing to worry about (this is only for developers, for now, so uv is expected either way) |
alinelena
approved these changes
Feb 6, 2025
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.
By default, uv will try to install Python 3.13 on a system with no existing Python 3 (e.g. scarf, before modules have been loaded).
Specifying different Python versions with
-pis discussed in the section below, but since people may copy and paste these to get started, it's probably safest to specify this here explicitly.