basedpyright

Pyright is only for type-checking and it lacks many features you'd expected from a modern LSP (I forgot which). Hence, it was forked and someone created basedpyright to fix it: https://github.com/DetachHead/basedpyright

last time i looked the people were recommending basedpyright: https://github.com/DetachHead/basedpyright

Might be worth checking out https://github.com/DetachHead/basedpyright But I’ve had the same issue with too many warnings, mypy is better at understanding Python but even slower.

Everyone is already recommending pyright, but I'll suggest checking the "based" community fork: https://github.com/detachhead/basedpyright Besides re-adding features that Microsoft makes exclusive to pylance, it tweaks a number of features that IMO makes pyright work better out the box: https://docs.basedpyright.com/latest/benefits-over-pyright/p...

> If you enjoy a rabbithole, look at how much DRM there is in Pylance So just don't use it? The linked discussion points to Basedpyright https://github.com/detachhead/basedpyright/ as the best free alternative right now (with some additional features around Python optional typechecking that aren't even in Pylance itself).

Instead of Pyright use Based Pyright for anything that isn't Code, and in Code (not Codium) you can use Pylance instead. https://github.com/DetachHead/basedpyright

Haven't used it much yet, but basedpyright appears to be a promising fork of pyright https://github.com/DetachHead/basedpyright

basedpyright: https://github.com/DetachHead/basedpyright (assuming you can't/don't use MSFT's pylance)

One of the things that comes to mind here is the fact that the default Python extension for VS Code is, perhaps surprisingly to many, not open source. https://github.com/microsoft/pylance-release While it's possible to fork VS Code, it is not possible to fork VS Code and provide a seamless onramp towards a Python editing experience that is fully open source, because users are used to the nuances of the closed-source Pylance experience in VS Code proper. You could use the minified/compiled Pylance plugin in your fork, but you'd have no way to expand its capabilities to new hooks your fork provides. Microsoft's development process would always be able to move faster than a fork, because it could coordinate VS Code internal API development with its internal Pylance team, and could become incompatible with forks at any time. It's worth re-rea

In the interim, check out basedpyright [1]. It's an up-to-date fork of pyright with some improvements, less arbitrary limitations, and does not require npm to install. [1] https://github.com/detachhead/basedpyright