Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Which Python type checker should I use?

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 83 posts

Re: Ask HN: Which Python type checker should I use?

#31

Post by ZiiS »

drekipus wrote: post #10

Pyright is the Microsoft provided lsp: does anyone else feel uneasy about using this? Especially given the EEE playbook "that we definitely won't do this time" - would love to have a discussion on this if someone could talk me into using it. I just use a combination of black, flake, and mypy. Apparently ruff is quite good as well. For lsp I use Jedi, which actually worked faster on my company's code base than pyright…

Pylance is their proprietary LSP; pyright is an opensource (but MS managed) typechecker (which pylance uses).

Re: Ask HN: Which Python type checker should I use?

#33

Post by winrid »

damezumari wrote: post #28

I would not personally use any of them. Typed python in previous workplace was pretty much shitshow, and if starting from scratch instead of untyped codebase it might be worth it, maybe, for some specific cases, but in general combination of bad library typing and bad type checking tools leads to horrible user experience. So going forward my personal projects continue to be ducktyped, and if I care about types, I use…

Even the Stripe API types are terrible.

I'm moving away from Python for my large projects...

Re: Ask HN: Which Python type checker should I use?

#34

Post by emblaegh »

damezumari wrote: post #28

I would not personally use any of them. Typed python in previous workplace was pretty much shitshow, and if starting from scratch instead of untyped codebase it might be worth it, maybe, for some specific cases, but in general combination of bad library typing and bad type checking tools leads to horrible user experience. So going forward my personal projects continue to be ducktyped, and if I care about types, I use…

Whatever bad experience you get from the (admittedly) immature tooling, pales in comparison to the intense discomfort or working with an untyped Python code base of even moderate size, specially ones written by many different contributors.

Re: Ask HN: Which Python type checker should I use?

#35

Post by vosper »

drekipus wrote: post #10

Pyright is the Microsoft provided lsp: does anyone else feel uneasy about using this? Especially given the EEE playbook "that we definitely won't do this time" - would love to have a discussion on this if someone could talk me into using it. I just use a combination of black, flake, and mypy. Apparently ruff is quite good as well. For lsp I use Jedi, which actually worked faster on my company's code base than pyright…

How do you imagine that EEE could be applied to a type checker?

Re: Ask HN: Which Python type checker should I use?

#36

Post by crucialfelix »

josebama wrote: post #25
fbdab103 wrote: post #8

Would also be interested in what is friendly with Django. Using VSCode + the Python extension, the default checker (Pylance?) just pukes on the ORM magic.

To get the type checker to work with Django you need to install django-stubs[1]. It works great with mypy, but should also work well with pyright. [1]: https://github.com/typeddjango/django-stubs

The types will work in pyrite, but there is no pyright support for plugins, so the Django magic doesn't get typed correctly.

I'm considering switching to pyright, probably by rewriting code that uses this magic.

Or running both in ci with different configurations.

Re: Ask HN: Which Python type checker should I use?

#38

Post by mastazi »

tentacleuno wrote: post #13
drekipus wrote: post #10

Pyright is the Microsoft provided lsp: does anyone else feel uneasy about using this? Especially given the EEE playbook "that we definitely won't do this time" - would love to have a discussion on this if someone could talk me into using it. I just use a combination of black, flake, and mypy. Apparently ruff is quite good as well. For lsp I use Jedi, which actually worked faster on my company's code base than pyright…

Can the extension be used on VSCodium builds? If memory serves, C# tooling extensions are proprietary and are subject to unfortunate treatment when using open-source builds of VSCode.

Pyright works for me on VSCodium, Pylance doesn't.

Re: Ask HN: Which Python type checker should I use?

#39

Post by mastazi »

mdasen wrote: post #29
giantzoc wrote: post #26

Earlier quoted context omitted.

You are correct. It is not supported on vscodium.

Yea, and if you're a company making more than $1M in revenue or have over 250 PCs, then you need a commercial license. Microsoft definitely seems to be pushing proprietary VSCode extensions where it's free to get users hooked on the product (and kill competitors) and then charge companies lots of money for the tools they got everyone hooked on because they appeared to be free.

are you talking about Pyright or Pylance?

Re: Ask HN: Which Python type checker should I use?

#40

Post by Vuizur »

mastazi wrote: post #39
mdasen wrote: post #29

Earlier quoted context omitted.

Yea, and if you're a company making more than $1M in revenue or have over 250 PCs, then you need a commercial license. Microsoft definitely seems to be pushing proprietary VSCode extensions where it's free to get users hooked on the product (and kill competitors) and then charge companies lots of money for the tools they got everyone hooked on because they appeared to be free.

are you talking about Pyright or Pylance?

He's talking about the new C# extension, Pyright and Pylance are free for everyone.
Post reply on HN