Skip to content
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

--workdir: resolve symlinks or warn about it #1169

Closed
blueyed opened this issue Feb 21, 2019 · 0 comments
Closed

--workdir: resolve symlinks or warn about it #1169

blueyed opened this issue Feb 21, 2019 · 0 comments

Comments

@blueyed
Copy link
Contributor

@blueyed blueyed commented Feb 21, 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.

blueyed added a commit to blueyed/tox that referenced this issue Feb 22, 2019
blueyed added a commit to blueyed/tox that referenced this issue Feb 22, 2019
blueyed added a commit to blueyed/tox that referenced this issue Feb 23, 2019
blueyed added a commit to blueyed/tox that referenced this issue Feb 23, 2019
gaborbernat added a commit that referenced this issue Feb 24, 2019
* toxworkdir: use realpath

Fixes #1169.

* ensure tox.ini

* no need for --help anymore

* use tmp_path

* changelog
@tox-dev tox-dev locked and limited conversation to collaborators Jan 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants