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
This causes it to pick up the setup.py file as a potential test file, and even though it will contain no tests, importing setup.py during testing can have unwanted side effects. (For one, it makes setuptools a dependency of the test environment, where it would otherwise normally not be.)
Unfortunately, reading through the pytest documentation, it doesn't seem as though there's an easy way to exclude specific files once they've been caught up in an inclusion glob.
The text was updated successfully, but these errors were encountered:
The default python_files globs are test_*.py and *_test.py, so unless there's some reason it isn't feasible to name all test files using one of those two patterns, it might be best to just remove the python_files = "*.py" line and use the default value.
As noted in aboutcode-org/saneyaml#15, the
pytest
configuration inpyproject.toml
currently configures it to pick up*.py
:https://github.com/nexB/skeleton/blob/acf94b360d675087195b7f216f4bee4401609729/pyproject.toml#L10
https://github.com/nexB/skeleton/blob/acf94b360d675087195b7f216f4bee4401609729/pyproject.toml#L43
This causes it to pick up the
setup.py
file as a potential test file, and even though it will contain no tests, importingsetup.py
during testing can have unwanted side effects. (For one, it makessetuptools
a dependency of the test environment, where it would otherwise normally not be.)Unfortunately, reading through the pytest documentation, it doesn't seem as though there's an easy way to exclude specific files once they've been caught up in an inclusion glob.
The text was updated successfully, but these errors were encountered: