Description
VS Code version
1.63.2
Extension version
2021.12.1559732655
OS type
Windows
OS version
Windows10 H1 Built 1943
Python distribution
Other
Python version
3.8.5
Language server
Default
Expected behaviour
The selected linter should've been ran and its settings in the settings.json file should've been respected.
Actual behaviour
Pylint is not ran, its settings are not respected, VSCode does not show pylint messages. Such exist as verified through the command line.
Steps to reproduce
I haven't tried to recreate it on another machine. My setup is:
- Windows 10
- WSL V1 with Ubuntu 18.04
- remote wsl extension
- pyenv python environment 3.8.5
After the december update of VSCode, might've been 1.63.1 even, the remote environment became completely unusable. VSC decided that it is github.dev or something and ran the workspace in partial mode. I deleted everything on the local os and in the WSL and reinstalled from scratch. Currently the environment is normal, but the python extension does not respect the choice of pylint as a linter and does not run it when I execute the "Run linter" command from the command palate.
Current settings.json on the remote environment:
{
"workbench.startupEditor": "none",
"editor.accessibilitySupport": "on",
"python.analysis.autoImportCompletions": true,
"python.analysis.autoSearchPaths": true,
"python.analysis.completeFunctionParens": true,
"python.analysis.useLibraryCodeForTypes": true,
"python.formatting.provider": "black",
"python.linting.enabled": true,
"python.linting.lintOnSave": true,
"python.linting.pylintEnabled": true,
"python.linting.pylintUseMinimalCheckers": false,
"python.linting.pylintArgs": [
"--rcfile",
"/mnt/c/Users/<username>/<project_name>/.vscode/.pylintrc"
]
// "python.linting.pylintCategorySeverity.error": "Error",
// "python.linting.pylintCategorySeverity.fatal": "Error",
// "python.linting.pylintCategorySeverity.warning": "Warning",
// "python.linting.pylintCategorySeverity.refactor": "Information",
// "python.linting.pylintCategorySeverity.convention": "Information"
}
Logs
No response
Code of Conduct
- I agree to follow this project's Code of Conduct