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
FileNotFoundError on older Pythons with flake8 3.2 #852
Comments
I'm able to replicate this failure on my local workstation. |
I can't tell when this issue started. It looks like there was a clean build 5 days ago, and the first failure happened about an hour ago, so something apparently changed in Travis-CI and on my machine in that period. I haven't run brew update this week. I've tried downgrading pip and tox and setuptools, but to no avail. |
I can replicate the failure surgically running this command:
Even if I go back to the code where the last clean build happened, I get the error, so it's definitely something environmental triggering the failure. I noticed that pytest was recently updated to 3.0.4, so I tried downgrading pytest to 3.0.3, but that did not help. |
I grabbed the requirements specifically from the list of requirements emitted in the last clean build (thanks pytest for reporting that information), and the test passes. Now I should be able to bisect those changes and find the offending package. |
Installing flake8==3.2.1 and pyflakes==1.3.0 causes the failure whereas flake8==3.0.4 and pyflakes==1.2.3 does not. |
It seems that with these later versions of flake8 and pyflakes installed, the
|
And I've confirmed, running that same test with pyflakes 1.2.3 and flake8 3.0.4, the test passes. |
Here are the differences in pyflakes and the differences in flake8. |
One noticeable difference in flake8 is it now imports setuptools in flake8/main/debug.py. Indeed, if I comment out that import, the problem goes away. |
Running pdb, I can see the stack when that import is invoked. It's early in the pytest setup:
|
In the context of the test, |
I notice that the issue does not occur on Python 3.3+ because
|
This latest commit fixed most of the failures, but something is still failing on pypy3. Aah. It's support for Python 3.2 dropped from pip. Separate issue. |
…the empty path from being added to sys.path per pytest-dev/pytest#2104. Fixes #852. Also use 'usedevelop' as the setuptools.tests.fixtures aren't available in a standard install.
Recently and inexplicably, tests have started failing on Python 3.2 and earlier in Travis-CI, such as seen in this run. Mainly one test is failing:
I have no idea why it's failing.
The text was updated successfully, but these errors were encountered: