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.

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

Can uv auto recognize rye's Python installation? #4644

Open
jfcherng opened this issue Jun 29, 2024 · 2 comments
Open

Can uv auto recognize rye's Python installation? #4644

jfcherng opened this issue Jun 29, 2024 · 2 comments
Labels
configuration Settings and such needs-decision Undecided if this should be done

Comments

@jfcherng
Copy link
Contributor

jfcherng commented Jun 29, 2024

For example, I have C:\Users\jfcherng\.rye\py\[email protected] but it won't be listed on uv toolchain list and I can't do uv venv --python 3.8. I can add C:\Users\jfcherng\.rye\py\[email protected] (and other installations) into PATH env variable but installation directories are bound to major.min.patch version. That means I have to update PATH every time when there is a patch version update.

I know there is uv toolchain install but that feels like a duplication to me since I already have a copy under C:\Users\jfcherng\.rye\py.

Just wondering how do people do it right?

@zanieb
Copy link
Member

zanieb commented Jun 29, 2024

I think we're unlikely to recognize toolchains provided by other tools, but I feel your pain here. We could probably make UV_TOOLCHAIN_DIR support C:\Users\jfcherng\.rye\py, it'd take some tweaks to our toolchain install parsing and opt-in but seems relatively reasonable.

@zanieb zanieb added needs-decision Undecided if this should be done configuration Settings and such labels Jul 1, 2024
@zanieb
Copy link
Member

zanieb commented Jul 1, 2024

cc @charliermarsh, thoughts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
configuration Settings and such needs-decision Undecided if this should be done
Projects
None yet
Development

No branches or pull requests

2 participants