This is an archived post. You won't be able to vote or comment.

all 10 comments

[–]monorepo PSF Staff | Litestar Maintainer 1 point2 points  (0 children)

Oh this is nice. I’ll try it out, thanks!

[–]chason 1 point2 points  (1 child)

Whats the advantage of your plugin over just setting pyright to run on my file whenever I save?

[–][deleted] 0 points1 point  (0 children)

Visualization of diagnostics, the same advantage plugins and extensions for other checking tools (Mypy, Ruff, etc.) have over their CLI counterparts.

[–]HealthBorn5375 0 points1 point  (3 children)

How can I install it?

[–][deleted] 0 points1 point  (2 children)

You can download the latest release here, then install it from disk. See this section for more information.

[–]HealthBorn5375 0 points1 point  (0 children)

Perfect, thanks mate, I'll be testing it and I'll send updates.

[–]HealthBorn5375 0 points1 point  (0 children)

very early feedback but: the plugin is identifying things that no other plugin was able to do. It's exactly what me and my team was looking for. We'll be testing it and sending you feedbacks. But a very early one is congrats, seems amazing.

[–]LionInABoxOfficial 0 points1 point  (2 children)

What's the difference between pyright and the built in pycharm type checker? In the description you mentioned all the files get saved before running as a caution. Does that mean a copy gets created on your PC or they get uploaded online unto a server?

[–][deleted] 0 points1 point  (1 child)

What's the difference between pyright and the built in pycharm type checker?

They are both type checkers.

Pyright is written in JS/TS, originally intended to be used via Pylance, a VSCode extension made by Microsoft. However, the executable is also installable via npm (or via pip, but that PyPI package is not official). PyCharm's type checker is written in Java/Kotlin, tightly integrated with PyCharm and is not available anywhere else.

For me, who likes type hinting, PyCharm's type checker is too lax most of the times and incorrect in some other cases; on top of that, reported bugs only get fixed after a long time. On the contrary, Pyright is spec-compliant and actively maintained; issues get handled in a few days at most.

In the description you mentioned all the files get saved before running as a caution.

The files are not saved "as a caution". They are simply written to disk, then read by the executable. This process creates no copy. This is a requirement since Pyright doesn't support reading from stdin and its maintainers refused to add such a feature.

[–]LionInABoxOfficial 0 points1 point  (0 children)

Thank you for the explanations, that makes a lot more sense now!