-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
lib64 directory is no longer symlinked to lib? #1751
Comments
@abn this is the intention and by design. The lib does not have to be linked to the lib64 directory. There are two separate library paths, called |
@gaborbernat thanks for the clarification. I was unsure if this was by design. The confusion arose as the |
Not sure who added the downstream changes; is it an OS patch or upstream CPython? I think the intention here is to keep them separate; that being said merging them can also have some merit 🤷♂ though I consider it more error-prone. |
I am not entirely sure on that one. But I do agree that keeping them separate is probably the better choice here. |
Issue
Came across this issue while debugging tox environment creation issues. It would seem that when using
virtualenv==16.7.10
or simplypython -m venv
, thelib64
directory was a symlink to thelib
directory as expected. However, invirtualenv==20.0.14
, this is no longer the case. Here,lib64
is created as a directory.For example, the following will reproduce the issue.
The following, is a snippet from the output.
Environment
Provide at least:
OS:
Fedora release 31 (Thirty One), Linux 7ab2b964bf3a 5.5.10-200.fc31.x86_64 #1 SMP Wed Mar 18 14:21:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
pip list
of the host python wherevirtualenv
is installed:Output of the virtual environment creation
Make sure to run the creation with
-vvv --with-traceback
:The text was updated successfully, but these errors were encountered: