We Keep Coding

Python in VSCode: Syntax highlighting, tabs and no pep8

I have reinstalled my PC and get crazy about initialising VScode correctly.
I want to use syntax highlighting in Python, I use tabs instead of space and I don't want to see pep8 warnings.
After ours of debugging, I dont have syntax highlighting, errors due to tabs and I see all pep8 warnings.🙈
I have installed Python and Pylance as extensions and currently, my settings.json looks like this:
{
"[python]": {
"editor.insertSpaces": true,
"editor.tabSize": 4
},
"python.linting.enabled": false,
"files.exclude": {
"**/.classpath": true,
"**/.project": true,
"**/.settings": true,
"**/.factorypath": true
},
"java.semanticHighlighting.enabled": true,
"terminal.integrated.enableMultiLinePasteWarning": false
}
Is there anybody who can knows what to do?
Edit: After reloading, the messages about space vs tabs have disappeared.

If you want to ignore the messages prompted by the pylint you can add this in the settings.json:
"python.linting.pylintArgs": ["--disable", "C"],
And it means this:
Convention (C)
Refactor (R)
Warning (W)
Error (E)
Fatal (F)
And you can do it like this to disable multi types of the message:
"python.linting.pylintArgs": ["--disable", "C,R,W"],

I can't change variable colors One Dark Pro Visual Studio Code for Python

I'm having an issue regarding Visual Studio Code OneDark Pro theme. I would like to change the color of variables (only variables I declare, not method calls, etc. but when I try to do this using
"editor.tokenColorCustomizations": {
"textMateRules": [
{
"scope": "source.python",
"settings": {
"foreground": "#E06C75"
}
}
]
}
I get this (I wrote a code sample to illustrate what is happening):
As you can see, colons are in red, every variables even the "for i in..." and the full "os.system.getcwd()" are in red.
I only want the variables I declare to be in red. How can I do that ?
Thank you in advance!

You can modify the editor color in VSCode with Syntax Highlighting like this:
"editor.tokenColorCustomizations": {
"variables": "#c3e01f"
},
Or the Semantic Highlighting like this:
"editor.semanticTokenColorCustomizations": {
"[The Theme Name]": {
"rules": {
"variable.declaration": "#c3e01f"
}
}
},
If you don't know the scope of the object which you want to customize, you can use the built-in tool in VSCode: Developer: Inspect Editor Tokens and Scopes(Command Palette).
And I think this article and this one can help you understand the color customization in the VSCode.

How do I turn off the "Evaluating: plt.show() did not finish after 3.00s seconds." warning in the VsCode debugger?

I often debug my python code by plotting NumPy arrays in the vscode debugger.
Often I spend more than 3s looking at a plot. When I do vscode prints the extremely
long warning below. It's very annoying because I then have to scroll up a lot
all the time to see previous debugging outputs. Where is this PYDEVD_WARN_EVALUATION_TIMEOUT
variable? How do I turn this off?
I included the warning below for completeness, thanks a lot for your help!
Evaluating: plt.show() did not finish after 3.00s seconds.
This may mean a number of things:
This evaluation is really slow and this is expected.
In this case it's possible to silence this error by raising the timeout, setting the
PYDEVD_WARN_EVALUATION_TIMEOUT environment variable to a bigger value.
The evaluation may need other threads running while it's running:
In this case, it's possible to set the PYDEVD_UNBLOCK_THREADS_TIMEOUT
environment variable so that if after a given timeout an evaluation doesn't finish,
other threads are unblocked or you can manually resume all threads.
Alternatively, it's also possible to skip breaking on a particular thread by setting a
pydev_do_not_trace = True attribute in the related threading.Thread instance
(if some thread should always be running and no breakpoints are expected to be hit in it).
The evaluation is deadlocked:
In this case you may set the PYDEVD_THREAD_DUMP_ON_WARN_EVALUATION_TIMEOUT
environment variable to true so that a thread dump is shown along with this message and
optionally, set the PYDEVD_INTERRUPT_THREAD_TIMEOUT to some value so that the debugger
tries to interrupt the evaluation (if possible) when this happens.

If found a way to adapt the launch.json which takes care of this problem.
{
"version": "0.2.0",
"configurations": [
{
"name": "Python: Current File",
"type": "python",
"request": "launch",
"program": "${file}",
"env": {"DISPLAY":":1",
"PYTHONPATH": "${workspaceRoot}",
"PYDEVD_WARN_EVALUATION_TIMEOUT": "500"},
"cwd": "${workspaceFolder}",
"console": "integratedTerminal"
}
]
}

based on here, you can simply set the timeout parameter of debug configuration(launch.json). for example, sth like this:
{
"version": "0.2.0",
"configurations": [
{
"name": "Python: Django",
"type": "python",
"request": "launch",
"timeout": 10,
"program": "${workspaceFolder}/src/manage.py",
"args": [
"runserver"
],
"django": true
}
]
}

If you are keen to surpress the warning, you'd go like this:
In this documentation, point 28.6.3, you can do so:
https://docs.python.org/2/library/warnings.html#temporarily-suppressing-warnings
Here's the code if the link dies in the future.
import warnings
def fxn():
warnings.warn("deprecated", DeprecationWarning)
with warnings.catch_warnings():
warnings.simplefilter("ignore")
fxn()
You should be ready to go with a simple copy paste.

PEP8 plugin breaks my Type Hint code in Sublime 3

I had to disable the format on save setting, because Python PEP8 Autoformat plugin reformatted my code, causing a syntax error.
My code (focus on last lines):
from typing import List, Tuple
from my_enent import MyEvent
def my_preprocessor(raw_event, context: object, env: MyEnv) \
-> Tuple[dict, VideoFreezeEvent]:
if isinstance(raw_event, dict) and 'Output' in raw_event:
# comments
raw_state_machine_event = json.loads(raw_state_machine_event['Output'])
# comments
parallel_outputs = raw_state_machine_event.get(
'my_data').get('parallel_outputs')
if len(parallel_outputs) > 0:
state_machine_event = parallel_outputs[0]
my_list: List[MyEvent] = [
my_util.populate_dataclass(MyEvent, event)
for event in parallel_outputs
]
another_event = events_list[0]
After the plugin reformats the code, the relevant part of the code that causes the syntax error becomes:
if len(parallel_outputs) > 0:
state_machine_event = parallel_outputs[0]
my_list:
List[MyEvent] = [
my_util.populate_dataclass(MyEvent, event)
for event in parallel_outputs
]
another_event = events_list[0]
How can I prevent/teach the plugin to not break this code please?
Some package settings that might be the way through, if a passage exists in the first place:
{
// list codes for fixes; used by --ignore and --select
"list-fixes": false,
// do not fix these errors / warnings (e.g. [ "E501" , "E4" , "W"])
"ignore": [],
// select errors / warnings (e.g. ["E4", "W"])
"select": [],
// Maximum line length
"max-line-length": 79
}

Your linter sounds like it is rather out of date, as it neither recognizes the walrus operator := or your type annotations. Looking at the plugin's Package Control page, you can see that up at the top it says "MISSING", which means the source code repo is gone, most likely because it's not being maintained anymore. The package was last modified 5 years ago, and there are no recent installations, so there's very strong evidence it's dead.
As a replacement plugin, I'd highly recommend Anaconda
(not related to the Anaconda Python distribution). It works great (mostly), is under active development with frequent updates, bugfixes, and new features, and does code completion and code intelligence along with linting/autoformatting. The website goes through all the configuration you need to do, and how to turn off and on the different features. There are several different linting/formatting options to choose from, including AutoPEP8, PyFlakes, and PyLint. I really like it.
(And no, I'm not associated with it or its author in any way.)

I found workaround. Go to plugin settings (Preferences -> Package Settings -> Python PEP8 Autoformat -> …), add ignore rule, e.g.:
{
// Workaround for typing hints
"ignore": ["E701"],
}
I guess it ignores this warning: https://www.flake8rules.com/rules/E701.html
Seems not very harmful.

I installed Black via pip, and used sublack Sublime plugin, which appears to be running smoothly.
Anaconda Sublime plugin suggested by MattDMo is cool, but a bit slow (with the default settings at least), any my Mac laptop is fairly new.

Visual Studio Code> Python > Black formatting does not run on save

Although I seem to have configured both linitng and formatting properly, the linting runs but the black formatting does not.
"python.linting.flake8Enabled": true,
"python.linting.flake8Args": [
"--max-line-length=110"
],
"python.linting.lintOnSave": true,
"python.formatting.provider": "black",
"python.formatting.blackPath": "/usr/local/bin/black",
"python.formatting.blackArgs": [
"--line-length",
"110"
],
"editor.formatOnSave": true,
I have checked, that black is properly configured and I can run the formatting from the command-line without issues.
But when saved in the IDE, black does not format the file. It also does not complain, there are no error-messages that pop up and nothing showing up in the logs. It just does not run the formatting at all.
I am running this insisde a docker-container using remote-editing: not sure, if this makes a difference.
The black-version is:
black>=19.3b0
and the vscode-version is 1.36.1.
Thx for any help, as right now I am pretty clueless, why the black-formatting does not run...

The line argument for black is wrong, it should be
--line-length=120
according to https://stackoverflow.com/a/58048911/4435175.

Late answer, in case it helps anybody. I had the same problem and resolved it as below
I needed to have this line in user settings.json
"editor.defaultFormatter": "ms-python.python"
Otherwise, I guess, the formatting was overwritten by my default formatting option which was
"editor.defaultFormatter": "esbenp.prettier-vscode",
So my overall settings for formatting related stuff were as below
"editor.defaultFormatter": "esbenp.prettier-vscode",
"editor.formatOnSave": true,
"[python]": {
"editor.formatOnSave": true,
"editor.defaultFormatter": "ms-python.python"
},
"[javascript]": {
"editor.formatOnSave": true,
"editor.defaultFormatter": "esbenp.prettier-vscode"
},
"python.formatting.provider": "black",
"python.formatting.blackPath": "/home/<user>/anaconda3/bin/black",
This line "editor.defaultFormatter": "ms-python.python" could also have been activated as below from VS-Code command-pallette (Ctrl + shift + P).
Format Document with > Configure Default formatter > Select Python

But here is a wild guess: I started the dockerd manually from the command-line using sudo: This gave me all kind of weird issues (files created from inside the container e.g. migrations or cache-files ended up being owned by root. I recently moved the dockerd into a service, now suddenly black is running on save. The root of all evil could have been rights-issues, that come from the fact that the dockerd was run as sudo and not as a service.

I add the blackPath:
"python.formatting.provider": "black",
"python.formatting.blackPath": "C:/conda/Scripts/black.exe",
and solve this issue.
I use miniconda.