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 ?
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
fancy-daybreak-62348
12/20/2023, 1:19 AM
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?
fancy-daybreak-62348
12/20/2023, 1:24 AM
ah nvm, it’s the issue where i need to give protobuf_sources the explicitly types-protobuf dep