Analysis engine should not provide linter messages if linting is disabled

[DonJayamanne]

The setting python.linting.enabled is set to false
However I'm still getting linter error messages from the analysis engine.

[MikhailArkhipov]

You always get them since they are syntax errors, not 'linting'. Technically 'linting' is not a syntax check, it is deeper analysis (term comes from C++ Lint https://en.wikipedia.org/wiki/Lint_(software)).

There is no way to suppress syntax check as there is no way to do it in VS. Said flag eventually will be used to activate actual linting (i.e. uninitialized variables, style errors etc).

[patrys]

I like these errors and I like the fact that they are not only reported for the currently opened files but:

• The Analysis Engine is reporting problems for files in my virtualenv. Packages such as astroid and pylint contain a lot of test files that are intentionally invalid.

• The Analysis Engine is reporting problems for files in the node_packages directory. That in turn contains node-gyp which only supports Python 2.7 so it results in a nice list of syntax errors.

[brettcannon]

Right, and that's the tricky bit with this. Does the VCS service in VS Code let us query if a file is ignored by the current VCS? If so then we could use that to filter out non-opened files from being checked for syntax errors.

[DonJayamanne]

@patrys I've created a separate issue for the issue you have reported.

[MikhailArkhipov]

OK, #1861 and #1860 address the issues. 'linting' flag is not the same as syntax check. Closing this one.