Is it possible to disable an inspection for the whole file in PyCharm?
The reason this is needed is when dealing with py.test. It uses fixtures which appear to shadow function parameters, and at the same time cause unresolved references. e.g.:
from myfixtures import user # Unused import statement warning
def test_is_awesome(user): # Shadows name 'user' from outer scope warning
assert user.is_awesome()
There is also other warnings from py.test, such as using pytest.raises()
causes a "Can not find reference 'raises'" in pytest.py.
Maybe there's another way to fix these problems? Maybe I'm using py.test incorrectly?
Disable inspectionsIn the Settings/Preferences dialog ( Ctrl+Alt+S ), select Editor | Inspections. Locate the inspection you want to disable, and clear the checkbox next to it. Apply the changes and close the dialog.
Tracking PEP8 rules So, as you can see, PyCharm supports PEP8 as the official Python style guide. If you explore the list of inspections ( Ctrl+Alt+S - Inspections), you will see that PyCharm launches the pep8.py tool on your code, and pinpoints the code style violations.
By default, PyCharm uses the TSLint package from the project node_modules folder and the tslint. json configuration file from the folder where the current file is stored. If no tslint. json is found in the current file folder, PyCharm will look for one in its parent folders up to the project root.
Code inspections In PyCharm, there is a set of code inspections that detect and correct abnormal code in your project. The IDE can find and highlight various problems, locate dead code, find probable bugs, spelling problems, and improve the overall code structure.
Is it possible to disable an inspection for the whole file in PyCharm?
Yes. This answer is for this question only (and not about "Maybe there's another way to fix these problems? Maybe I'm using py.test incorrectly?").
Alternatively (may work or may not: depends on actual inspection .. and I'm not sure if it actually works in PyCharm this way -- not a PyCharm user myself unfortunately)
This is how it looks in PhpStorm (screenshot shows "suppress for statement" option and not "suppress for whole file"):
Related: https://stackoverflow.com/a/20803118/783119
To answer the "Maybe I'm using py.test incorrectly?" question:
Importing fixtures is not the best pattern to follow. Instead it is better to put fixtures in a conftest.py file of the package which needs them. If a fixture is used in two packages just put a conftest.py in their parent directory and put the fixture in there. This should get rid of the unused import and shadowing warnings.
As for the pytest.raises
namespace issue, I don't think there's a solution to this currently. This is something that pylint suffers as well (and I think there's an effort to create a py.test plugin to pylint to address these things). So I think at the end of the day the linter will still need to know a little about py.test.
I found that putting the per statement inspection:
...
# noinspection PyUnusedLocal
instance = mommy.make(Contact)
at the start of the file suppressed it for the whole file:
# noinspection PyUnusedLocal
from django.urls import reverse
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With