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
I've noticed a strange issue, where running an entry point wrapper script behaved differently with tox --workdir=symlink vs. tox --workdir=resolved_path (nedbat/coveragepy#777).
The main difference here appears to be with/how Python's import machinery behaves in this case.
Therefore I think it would be good to resolve any symlinks in the workdir, or at least trigger a warning.
The text was updated successfully, but these errors were encountered:
blueyed
added a commit
to blueyed/tox
that referenced
this issue
Feb 22, 2019
I've noticed a strange issue, where running an entry point wrapper script behaved differently with
tox --workdir=symlink
vs.tox --workdir=resolved_path
(nedbat/coveragepy#777).The main difference here appears to be with/how Python's import machinery behaves in this case.
Therefore I think it would be good to resolve any symlinks in the workdir, or at least trigger a warning.
The text was updated successfully, but these errors were encountered: