Can `uv` auto recognize `rye`'s Python installation?

[jfcherng]

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]

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]

cc @charliermarsh, thoughts?

[bluss]

Maybe rye can migrate to just reusing uv's toolchain feature (?) then it would be unified that way instead.

[jfcherng]

Maybe rye can migrate to just reusing uv's toolchain feature (?) then it would be unified that way instead.

Ah, yes, since rye uses uv, that may make more sense.