"python.linting.enabled": false ; still linting?
See original GitHub issueEnvironment data
- VS Code version: 1.60.1
- Extension version (available under the Extensions sidebar): v2021.9.1246542782
- OS and version: elementary OS 5.1.7 Hera (based on Ubuntu 18.04.6 LTS)
- Python version (& distribution if applicable, e.g. Anaconda): Python 3.8.11
- Type of virtual environment used (N/A | venv | virtualenv | conda | …): conda 4.10.3
- Relevant/affected Python packages and their versions: XXX
- Relevant/affected Python-related VS Code extensions and their versions: XXX
- Value of the
python.languageServer
setting: “Default”
[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'
), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected behaviour
"python.linting.enabled": false
should turn off linting
Actual behaviour
It does not?
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
- Set
"python.linting.enabled": false
- This is what I see (even after restarting):
(the Error Lens extension is activated)
Logs
Output for Python
in the Output
panel (View
→Output
, change the drop-down the upper-right of the Output
panel to Python
)
##########Linting Output - flake8##########
6,1,E,E265:block comment should start with '# '
7,80,E,E501:line too long (87 > 79 characters)
11,1,E,E303:too many blank lines (3)
18,1,E,E999:IndentationError: unexpected indent
18,2,E,E111:indentation is not a multiple of 4
18,2,E,E113:unexpected indentation
19,1,W,W293:blank line contains whitespace
20,1,W,W391:blank line at end of file
flake8
is not even enabled??
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (1 by maintainers)
Top Results From Across the Web
Linting Python in Visual Studio Code
To enable linters, open the Command Palette (Ctrl+Shift+P) and select the Python: Select Linter command. The Select Linter command adds "python.linting.<linter> ...
Read more >How to disable all python linting in VSCode - Stack Overflow
in my case just by going to the setting and searching for lint python in the search bar of the setting page and...
Read more >Linting | Python in Visual Studio Code
Cause: The Python extension is most likely using the wrong version of Pylint. Solution 1: (configure workspace settings to point to fully qualified...
Read more >Disable Python Linting in VS Code : r/vscode - Reddit
linting.enabled": false,. all in the settings.json file but even with these changed I am still getting error underlining in the editor.
Read more >Stylising your Python code: An introduction to linting and ...
Linting is a process for identifying bugs and stylistic errors in your code. The process is carried out by analysis tools called 'linters', ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you Kim. Since I no longer keep the workspace where the issue occurred (or the original settings) I think this issue can be closed now
The error doesn’t come from flake8, it comes from Jedi, the language server used to provide Intellisense. The Jedi implementation only supports Python 3, and is deactivated when using Python 2.7, so this behaviour makes sense. If you want to not get any Intellisense you can set the
python.languageServer
setting to"None"
, either in your user settings or your workspace settings.However, this doesn’t explain why you were getting flake8 linting messages in your original message, and I cannot replicate the behaviour.