-
Notifications
You must be signed in to change notification settings - Fork 284
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
Add support for # noqa #281
Comments
I also see that noqa is not respected, though I can't see any reason why it wouldn't be! Will need to dig in a bit more. |
I believe that it is because |
I am not sure what raises the "imported but unused" warnings, but that also doesn't seem to respect this comment. |
If you go about adding support for inline |
I created a quick-and-dirty pyls plugin called pyls-flake8 Once you install it with |
Same issue using the sure module which needs |
Well done @emanspeaks , you've helped me a lot! I think it'd be great if you'll create a PR for the '3rd party plugins' section in the README. |
This would also be a nice feature to work for warnings - much nicer to "wave through" a single line than to give Carte Blanche to all deprecation warnings project wide... ;) |
You are a champion. For anyone else dealing with this, my setup:
|
It does seem like at this point in time Flake8 has become the dominant linter. I'm not sure it was quite so convincing in the past. But perhaps now the defaults should swap over to that? Any objections? |
Is there still a plan to make flake8 the default some day? |
This is used at least by pycodestyle and flake8 to ignore a certain line from all linting. I personally use it when
from .conftest import * # noqa
in pytest.PyCQA/pycodestyle#476
The text was updated successfully, but these errors were encountered: