Disabling Pylance Linting, while keeping Pyright Type Checking.

[farzbood]

Hi,
I'm using Ruff as my Python Linter, so don't need Pylance Linting functionality, but want to keep using PyRight as static Type-Checking tool.

I've tried many settings/configurations to achieve that but no success yet!
Why are these Language Server/Linter and Type Checker so tight coupled anyway?!
Is there a way to do so or should just use another tool e.g: mypy instead?

Any suggestions would be appreciated.

[rchiodo]

Linting is kind of subjective, but if you set 'typeCheckingMode' to 'off', that should eliminate all of the errors that Pylance shows besides syntax errors. But intellisense and everything else would still work.

[rchiodo]

The python.analysis.ignore setting can also achieve a similar result. It ignores errors for everything that matches the ignore glob.

[farzbood]

I'm not sure have you got my point or even try your answer either, or what?

Bypassing Linting (error, warnings, etc.) while keeping Type-Checking (Type annotation/hint) in place and the suggestion is setting 'typeCheckingMode' to 'off' ?! really? (it's the other way and the default)

python.analysis.ignore is about Paths to analyze, not the way of treating the results, setting it to '*' (which is the only way to bypass Linting) supress everything (including Type-Checking)!

My guess is you at Pylance, think of Code Analysis in Python(a dynamic typed scripting language) as of a strong typed language that is not right.
What is Pylance anyway? Pylint + PyRight + ... that each of which belong to different use-cases and need to be manageable separately. remember (SoC).

[heejaechang]

I am not sure why reporting syntax errors is considered linting. usually linting means things like code styling errors.

[rchiodo]

It's not reporting them that's the problem. It's the fact that Ruff reports them too. There's unnecessary duplication.

[heejaechang]

I see, so ruff let users to control which errors to be reported including syntax errors, but we don't is the problem?

[heejaechang]

hmmm.. ruff doesn't allow disabling syntax error either?

The E999 rule was used to report syntax errors, allowing users to silence these reports via Ruff's disablement mechanisms. This release deprecates the E999 rule, which will be removed in a future release. Ruff will now always report all syntax errors it encounters, meaning users can no longer ignore them. The motivation for this change is to ensure users are always aware of syntax errors, as these prevent proper linting. By making syntax error reporting mandatory, we eliminate the risk of users missing these critical issues.

[rchiodo]

I see, so ruff let users to control which errors to be reported including syntax errors, but we don't is the problem?

No, the problem is the user has both Ruff and Pylance at the same time. They would like to use Ruff for syntax errors and all the other errors Ruff reports. For everything else they want to use Pylance. It only matter that we can't disable syntax errors. The user wants Ruff to show syntax errors.