3 ms·

TBH once you start using a fair number of dependencies (say, your average Flask or Django app) you end up with so many workarounds and flags like ignore_missing

by danjac 6y ago

TBH once you start using a fair number of dependencies (say, your average Flask or Django app) you end up with so many workarounds and flags like ignore_missing_imports that the benefit of mypy is marginal compared with other tools like flake and unit tests. I tend to use it more with libraries and less with applications.

junon 6y ago
Not to mention the performance. Perhaps it's improved since, but just a year ago it took an upwards of 10-20 seconds to type check a trivial repository.
- robbyt 6y ago
  Compared to the 10-20 hours I could spend debugging some stupid problem with passing objects to a function in the wrong order...
  - PeterisP 6y ago
    For that specific problem, using named parameters (even when not strictly necessary) is more helpoful.
  - junon 6y ago
    I didn't say don't use it. I was just saying it was a pain to use.
- incrudible 6y ago
  I've had a similar problems, pyright scales much better in my experience.
emptysea 6y ago
In my experience it’s been worth the trouble of writing partial type stubs for your project’s dependencies. And by partial I mean only typing the stuff you end up using, so if you just use one function from some huge, untyped package, just type that one part for now. The way I see it, you write the stub once, and then the API has less ambiguity and you get type checking.