You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
For example, I have
C:\Users\jfcherng\.rye\py\[email protected]
but it won't be listed onuv toolchain list
and I can't douv venv --python 3.8
. I can addC:\Users\jfcherng\.rye\py\[email protected]
(and other installations) intoPATH
env variable but installation directories are bound tomajor.min.patch
version. That means I have to updatePATH
every time when there is apatch
version update.I know there is
uv toolchain install
but that feels like a duplication to me since I already have a copy underC:\Users\jfcherng\.rye\py
.Just wondering how do people do it right?
The text was updated successfully, but these errors were encountered: