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
In tox-dev/tox#1706, I reported an issue where tox was unable to create a virtualenv for Python 3.5 when on a mounted file system from the host.
In that case, it seems that the test for "can symlink" happens on the local file system (and succeeds), but the attempt to create a symlink on the mounted filesystem fails.
The issue was only triggered in virtualenv creation on Python 3.5 (not 3.9) as seemingly symlinks are only needed for older Pythons.
The text was updated successfully, but these errors were encountered:
In tox-dev/tox#1706, I reported an issue where tox was unable to create a virtualenv for Python 3.5 when on a mounted file system from the host.
In that case, it seems that the test for "can symlink" happens on the local file system (and succeeds), but the attempt to create a symlink on the mounted filesystem fails.
The issue was only triggered in virtualenv creation on Python 3.5 (not 3.9) as seemingly symlinks are only needed for older Pythons.
The text was updated successfully, but these errors were encountered: