I'm using a combination of several linters in order to analyze my Python code using VSCode, including Pylint (alongside Ruff, CodeSpellChecker, and Pylance). Pylint is notably quite slow, although I have a rather large Python codebase, so this is reasonable. The issue for me is that Pylint causes the "quick fix" suggestions (from hovering over warnings or the shortcut Ctrl + .) to take upwards of 10 seconds to load. This happens on all VSCode warnings, even the ones that are generated by Ruff/Pylance (and are not a Pylint issue). I can't seem to pinpoint anything in the logs, but here is an example of what it looks like to hover over a warned element:
(The item was hovered at 4:54:51 and quick fix suggestions showed up at 4:54:59)
I only use Pylint for a small number of rules - I would be very happy to turn off Pylint "quick fix" suggestions entirely (but not the linter warnings), if that is something that I can configure. Please let me know of the best path to take.
I'm using a combination of several linters in order to analyze my Python code using VSCode, including Pylint (alongside Ruff, CodeSpellChecker, and Pylance). Pylint is notably quite slow, although I have a rather large Python codebase, so this is reasonable. The issue for me is that Pylint causes the "quick fix" suggestions (from hovering over warnings or the shortcut Ctrl + .) to take upwards of 10 seconds to load. This happens on all VSCode warnings, even the ones that are generated by Ruff/Pylance (and are not a Pylint issue). I can't seem to pinpoint anything in the logs, but here is an example of what it looks like to hover over a warned element:
(The item was hovered at 4:54:51 and quick fix suggestions showed up at 4:54:59)
Here is my configuration used, in case it helps:
I only use Pylint for a small number of rules - I would be very happy to turn off Pylint "quick fix" suggestions entirely (but not the linter warnings), if that is something that I can configure. Please let me know of the best path to take.