Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Using existing toolchain 3.13.0 #1426

Closed
PushUpek opened this issue Oct 30, 2024 · 0 comments · Fixed by #1429
Closed

Using existing toolchain 3.13.0 #1426

PushUpek opened this issue Oct 30, 2024 · 0 comments · Fixed by #1429

Comments

@PushUpek
Copy link
Contributor

Steps to Reproduce

  • install python 3.13
  • install rye 0.42.0 curl -sSf https://rye.astral.sh/get | RYE_INSTALL_OPTION="--yes" bash

Expected Result

Rye is using installed python 3.13 from system

Actual Result

#13 1.847 Installed binary to /pyroot/.rye/shims/rye
#13 1.849 Registering toolchain at /usr/local/bin/python [email protected] is not a valid toolchain
#13 2.174 
#13 2.174 Caused by:
#13 2.174     Toolchain [email protected] is not version compatible for internal use.

Version Info

#13 1.807   Rye Version: 0.42.0
#13 1.807   Platform: linux (x86_64)
#13 1.807   Internal Toolchain Path: /usr/local/bin/python

Stacktrace

No response
@PushUpek PushUpek mentioned this issue Nov 6, 2024
Merged
charliermarsh pushed a commit that referenced this issue Nov 7, 2024
@PushUpek
Fix compatibile toolchain (#1429)
7b8b101 
Resolves: #1426

This pull request includes an update to the compatibility range for the
supported Python versions in the `is_self_compatible_toolchain`
function.

*
[`rye/src/bootstrap.rs`](diffhunk://#diff-5e3b4dd9c9d72709e7551b50ad0bb8933e251e3f7ea71370a13637900c1b349cL285-R287):
Updated the supported Python versions to include cpython 3.13.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix compatibile toolchain PushUpek/rye
1 participant
@PushUpek