-
Notifications
You must be signed in to change notification settings - Fork 275
Tests no longer test local behavior #182
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
Comments
This issue probably emerged with Setuptools 34 due to pypa/setuptools#581. I've filed tox-dev/tox#467 to capture the unexpected behavior in tox. |
I've pushed changes to a branch demonstrating that my assertions about usedevelop and fixed pip versions correct the issue. |
Thanks a lot for noticing and looking into this. |
I have found a simpler workaround in
|
BTW, without either the workaround above or @jaraco's, I get errors like this:
|
Puts the current six checkout ahead of the PYTHONPATH for tests, else tests end up running six code installed in the tox environment. See: benjaminp#182
This issue no longer exists, due to 0d89d58, which because it's invoking diff --git a/tox.ini b/tox.ini
index fe56730..fa9c1a2 100644
--- a/tox.ini
+++ b/tox.ini
@@ -7,6 +7,7 @@ indexserver=
[testenv]
deps= pytest
commands= python -m pytest -rfsxX {posargs}
+skip_install = True
[testenv:flake8]
basepython=python And tests still pass. Moreover, late virtualenvs no longer get six by default, so the behavior that instigated this issue is no longer present as well. There's still an issue there are two different copies of six around when running the tox tests ( |
I've observed that the tests for six aren't actually testing new behavior... because they install the released version of six. This is because tox uses pip to install
.
and because six has manual versioning so the version in the repo is 1.10.0 (current release) which is already satisfied in a new virtualenv with setuptools installed. Worse yet, if one bumps the version to try to force the repo version to be installed, it triggers pypa/pip#4264.Adding
usedevelop=True
to the test environment seems to help with the first issue, causing the second issue to be triggered immediately.The text was updated successfully, but these errors were encountered: