Are there any tricks for getting VSCode to see generated Pyt

Question

Are there any tricks for getting VSCode to see generated Python code in `dist codegen` E g ` pb2 py` from `protobuf sources` Pointing VSCode at the virtualenv created by `pants export` gives me a mostly usable VSCode experience but I still get mypy errors inside VSCode about missing ` pb2` modules I found that I can add symlinks in the same directories as my ` proto` files that point to the generated files in `dist codegen` And add ` pb2 py` and ` pb2 pyi` to ` gitignore` But this feels uh pretty kludgy

high-yak-85899 · Answer

Yeah I was able to adjust a python interepreter setting for it Let me go dig up what I did

high-yak-85899 · Answer

I added this to my ` vscode settings json` file ``` python analysis extraPaths dist codegen lt source root here gt dist codegen lt another source root here gt ```

high-yak-85899 · Answer

After that it just worked tm

cool-printer-74432 · Answer

Hm that doesn t seem to work for me Do you have your ` proto` files in the same dir as code that uses them E g I have something like `awesome data proto` and `awesome stuff py` which has a `from awesome import data pb2`

high-yak-85899 · Answer

Yup I did

high-yak-85899 · Answer

` lt source root here gt ` came from `source root patterns` in my `pants toml` file

cool-printer-74432 · Answer

Still can t get it to work but I can see in the pylance trace logs that it at least sees the file Will have to keep debugging maybe I can get it to work Helpful to know that it works for someone else though thanks for the lead

quaint-forest-8735 · Answer

I ran into some problems getting this working at first and it turned out that PyCharm in our case wasn t able to resolve imports correctly when we had multiple top level python source roots as well as `dist codegen` once we isolated the python source tree everything worked

cool-printer-74432 · Answer

I ve asked on StackOverflow if anyone wants to follow along there <https stackoverflow com questions 72539844 vscode python autocomplete for generated code in separate directory>

cool-printer-74432 · Answer

I think I found a solution to this and an explanation why simply adding codegen paths to ` python analysis extraPaths ` Just Works for some PEP 420 implicit namespace packages means that Python will merge packages in different directories as long as none of the directories have an ` init py` So removing the ` init py` file from my checked in source directory means that Python can merge the checked in source and the codegen source as part of the same package and everything seems to work