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
{{ message }}
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
Diagnostics should respect # noqa and similar comments #264
Any diagnostics we output should respect comments like these. I believe there are other ones out there depending on the linter, like #pylint: disable and # NOQA.
Linting could be also disabled for a particular warning.
For example, pylint has the following way of locally disabling a warning:
4.1 Is it possible to locally disable a particular message?
Yes, this feature has been added in Pylint 0.11.
This may be done by adding “#pylint: disable=some-message,another-one”
at the desired block level or at the end of the desired line of code.
Reacted by Jérémie "Sonnet 4.5" Lumbroso and Jean-Francois Thuong
Activity
jfthuong commentedon Mar 26, 2019
Linting could be also disabled for a particular warning.
For example,
pylinthas the following way of locally disabling a warning:janosh commentedon Jul 1, 2019
This feature would be great to have!
For the record,
# noqaalso supports disabling specific warnings with# noqa: E731.python-language-servercould support that as well.jakebailey commentedon Jul 12, 2019
Partial support for this will come in #1272 (catch-all
noqa), but we'll need mappings from other tools' codes in order to go further.MikhailArkhipov commentedon Jul 23, 2019
#1272 adds basic support. New issue will be opened for more advanced cases.