After an incident I have reinstalled the default Python extension in VS code (for Windows 10) and pylint started to perform in a very strange way for any python file in my project (see an example below):

Pylint obviously works here as lines 4, 5 and 7 are shown as correct ones, while lines 1, 9, 10 and 11 are marked as containing errors.

But the list of these errors looks quite mysterious for me: I can not understand how any pylint option may be unrecognized or bad in a fresh unchanged installation?

Any suggestion how to fix the problem?

CodePudding user response：

The issue is in your configuration file or the option used to launch pylint, old-octal-literal does not exists anymore and pylint 2.14.0 started to warn about this kind of thing. See https://github.com/PyCQA/pylint/issues/6794.