-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Flake8 problems #307
Comments
Suggestion from #306 (comment)
|
Oh yeah, flake8 shows quite some problems when invoked explicitely! Not sure about |
Regarding the flake8 related failures themselves, it seems they're coming from the pytest plugin Actually, the |
Looks like the project was archived and this fork is active https://flakeheaven.readthedocs.io/en/latest/ I'm very unexperienced here 😁. What would be the advantage of using flakeheaven instead of flake8 directly? Is it that flakeheaven can be configured in pyproject.toml? Flake8 could be configured in its own config file. Also, what would it mean to decouple the linting from testing, that additional steps would need to be added to the github actions configuration? Locally for contributors I've seen that we're already suggesting to explicitely call flake8 in CONTRIBUTING.rst. |
There are two problems:
Describe the issue:
We have
--flake8
as a pytestaddopts
extra:...which I think is equivalent to the command line call
But when I run just
pytest
from the command line, it doesn't seem to pick up the extra addopts bit. All the tests pass with justpytest
, but there are failures when I runpytest --flake8
explicitly.Minimal Complete Verifiable Example:
pytest
, and observe the tests passing.pytest --flake8
(which should be equivalent to the above, given we are using addopts "--flake8"), but this time observe some tests failing due to flake8.Details (click to expand):
Anything else we need to know?:
I've noticed the same problem in #306
I might have done something silly by adding a separate
pytest.ini
file in #151, which might override or conflict with the pytest section insetup.cfg
. So this might have masked the problem for a while, but since I see the same problems with the new pyrpoject.toml configuration (#306) that can't explain everything.Environment:
conda list (click to expand):
The text was updated successfully, but these errors were encountered: