Pylint not working when language server is on

Environment data

• VS Code version: 1.38.0
• Extension version (available under the Extensions sidebar): 2019.9.34911
• OS and version: Windows 10
• Python version (& distribution if applicable, e.g. Anaconda): 3.7.3
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): venv
• Relevant/affected Python packages and their versions: pylint 2.3.1,
• Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): Language Server

Expected behaviour

Having linting, pylint and LS enabled in user settings should provide linting messages from both pylint and the LS.

Actual behaviour

Only LS is displaying linting messages. In order to get pylint to work, the workaround is to explicitly enable it in the workspace settings.

Steps to reproduce:

Enable pylint in the user settings, and make sure linting and the LS are enabled. Write a piece of code wrongly and notice that only the LS will display linting messages. We’d expect pylint to work as well.

cc @Anapo14

[darrickyee]

I am not sure what is meant by “this is how it has always worked”? As I understand it, the issue is that in the VSCode settings, the “Python > Linting: Pylint Enabled” checkbox is checked by default, but pylint is not actually enabled. So there is a discrepancy between what the Settings page shows and what the actual state of the settings is

Additionally, unchecking and re-checking the checkbox does not enable pylint (python.linting.pylintEnabled entry is deleted from settings.json when it is checked), so there is no way to enable pylint via the settings GUI. It seems the only way to enable it is to “manually” edit the settings.json file. I don’t think this is what the behavior was in previous versions?

[karthiknadig]

Verified fixed in main.