lib64 symlink can break subtly since 16.1 #1248
Comments
wouterdb
added a commit
to inmanta/inmanta-core
that referenced
this issue
Nov 30, 2018
* additional context capture * found bug in virtualenv 16.1 pypa/virtualenv#1248 * removed old entries from tox.ini
gaborbernat
pushed a commit
that referenced
this issue
Dec 3, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
tldr
When creating a virtualenv on a path that contains a symlink, the virtualenv break if this symlink is removed due to the changes made in 5d56014
context
When running tests, we create a workspace folder for each test, which has a symlink to a shared virtual env. The first test case populates the virtualenv. Then the first testcase's workspace is removed.
Prior to 16.1 this worked as expected. However, in 16.1 the lib64 symlink is absolute (but not canonical). So when the workspace of the first test is removed, the shared virtual env breaks. The next test run produces the error "module pip not found".
fix
revert the change on line 1622 (5d56014#diff-51642b24ac9529f4baa0f483fa257d2dL1622)
The text was updated successfully, but these errors were encountered: