Jukka Lehtosalo

I expect that types stub packages will be around for a long time, but hopefully they will be needed much less frequently in the future. It's not really something we...

@larroy @RouquinBlanc Did you actually have some files for mypy to type check? If you just use `mypy --install-types` without passing any files or directories, mypy will try to use...

Hmm it looks like the current behavior still seems somewhat problematic. What if we'd change `--install-types` to run the type check again after installing stubs? So `mypy --install-types --non-interactive src/`...

@john-bodley: > but would there be merit in making --install-types and --non-interactive the default (and provide the inverse --no--install-types and --interactive flags respectively) for consistency with versions < 0.900? I'm...

> For mypy to work correctly, won't the matching type packages always have to be installed? Not really. Users often decide to ignore missing stubs. There are many reasons to...

I am open to having an LSP server implementation included in mypy (eventually), but to completely replace dmypy we need to support all the existing functionality, or at least provide...

Wow, I didn't even know that `from .__init__ import ...` is a thing. If it works at runtime and does something useful, we should probably try to support it.

I think there is another case where type ignore comments still aren't being reported. Here are a few failing test cases: ``` [case testUnusedTypeIgnorePreservedAfterChangeInOtherModule1] # flags: --warn-unused-ignores [file main.py] import...

Ah, I forgot to mention that the test cases I mentioned above aren't specifically covered by #15043 yet. It's okay to leave fixing these for another PR, but we shouldn't...

LSP violations are generally tricky. Some of them are fairly benign and rarely cause issues, but others can be painful. As typeshed includes the subclass relationship present in the implementation,...