-
Notifications
You must be signed in to change notification settings - Fork 637
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
uv venv
does not create a lib64 directory
#3578
Comments
Does |
This is https://github.com/python/cpython/blob/b228655c227b2ca298a8ffac44d14ce3d22f6faa/Lib/venv/__init__.py#L135-L140 (basically, it's always created on 64-bit non-OS X POSIX) |
Lol thank you. Will fix. |
|
## Summary Closes #3578 (comment). ## Test Plan Verified that in the OpenSUSE test, we create both, and they're symlinks: ```text INFO: Creating virtual environment with `venv`... INFO: Installing into `venv` virtual environment... DEBUG Found a virtualenv named .venv at: /tmp/tmp4nape29h/.venv DEBUG Cached interpreter info for Python 3.10.14, skipping probing: .venv/bin/python DEBUG Using Python 3.10.14 environment at .venv/bin/python DEBUG Trying to lock if free: .venv/.lock purelib: "/tmp/tmp4nape29h/.venv/lib/python3.10/site-packages" platlib: "/tmp/tmp4nape29h/.venv/lib64/python3.10/site-packages" is_same_file(purelib, platlib): Ok(true) ```
Context
Platform: linux rocky 9
uv version:
0.1.42
Error when importing torch
Investigation
After investigation I discovered that:
uv venv foobar
does not create alib64
directory under the venv directorynvidia*
) inside itlib
and some other inlib64
lib64
is part of thesys.path
, however, it seems not used during the import of torch thus leading to the error abovepython -m venv foobar
, I noticed that thelib64
directory is created as a symlink to thelib
directoryuv venv
, when manually symlinking, everything is fineThe text was updated successfully, but these errors were encountered: