Is there a solution for getting VScodes mypy exten...
# general
f
Is there a solution for getting VScodes mypy extension to play nice with the types-xxx extensions? i tried using the mypy lock, point it at that mypy binary, and it doesn’t seem to ever know the types-* exist. Is the solution to simply add mypy to the default lock file / the lock file the code uses the execute ?
1
h
That default lockfile contains the type stubs? In that case yeah, you could try adding mypy to that lockfile and consuming it from there (See https://www.pantsbuild.org/docs/python-lockfiles#sharing-lockfiles-between-tools-and-code)
Pants is able to have separate "venvs" (actually pexes) for tools and code and compose them as needed, but vscode expects a single venv for code and tool
f
This ends building essentially a full PEX with mypy and my default lock, instead of just using my default resolve, which makes the first run of pants check really long, is that expected?
ah nvm, it’s the issue where i need to give protobuf_sources the explicitly types-protobuf dep