erictraut
commented
2 years ago Pylance is built on top of pyright, so they should give the same results.
There are a few reasons why you might see small differences:
- Pyright defaults "useLibraryCodeForTypes" to false, Pylance defaults it to true. You've explicitly set it to true, so that's not the issue.
- Pyright defaults "typeCheckingMode" to "basic", Pylance default it to "off". You've explicitly enabled diagnostics, so that's not the issue.
- Pyright is released two or three times each week, Pylance is released once a week. So sometimes pyright contains bug fixes or features that are slightly ahead of Pylance. That's probably not the issue here.
- Pylance bundles additional type stubs for some libraries that lack type information. These stubs are intended mostly for completion suggestions rather than type checking, but they can affect the type checking results. These stubs can be found in the microsoft/python-type-stubs repo, so you can download them and check the relevant ones into your local repo (in a "typings" directory so pyright finds them).
It looks like you're trying to use many of the strict type checking features including the "reportUnknownXXX" diagnostic checks. These checks rely on complete type information from libraries. If you are consuming any libraries that are not fully and accurately typed, you will likely run into problems. We normally recommend against using "useLibraryCodeForTypes" with type checking — and especially with strict-mode type checking — because it relies on type inference, and that often results in incomplete or inaccurate types.
ierezell
bschnurr
Environment data
A poetry project with a
pyrightconfig.json. There is no.vscodewithsettings.jsonnor any config in thepyproject.tomlExpected behaviour
Having the same problems in the "problem" tab and when running
pyrightby handActual behaviour
I fixed all the problems in the "problems" tab but when running pre-commit the pyright check didn't pass... So I tried to run it by hand (
poetry run pyright) and indeed, pyright (by hand) gives "new" errors (not shown in the problems tab)Pyright config
Logs
Code Snippet / Additional information