Added support for bootstrapping with specific toolchain version #606
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.
This is a pretty messy change that changes how bootstrapping can work. This in reference to #605
The motivation here is that a user can bootstrap rye and point it to a specific Python version. Today this already works with
RYE_TOOLCHAINto a toolchain that is available on the file system. However this now also addsRYE_TOOLCHAIN_VERSIONwhich registers a specific toolchain rather than the current latest version. This only allows a toolchain to be registered that is compatible with the version range supported by the system.