Thank you for this hint @mati-nvidia. As I was using Create I found my package at C:\Users\martin\AppData\Local\ov\data\Kit\Create.Next\2022.3\pip3-envs\default\yaml. Adding this path to settings.json didn’t resolve my issue.
When copying the the yaml package into the workspaceFolder of my extension and adding {workspaceFolder}/yaml Pylance finds the package. But this is no practical solution.
I then found this pylance issue here.
The yaml package comes with a .pydwhich seems like it can not be interpreted by pylance.
I could switch to other yaml packages as pyyaml but didn’t succeed installing any alternative via pipapi.
I’m surprised that didn’t work. It’s effectively the same as putting it in the workspace. Did you try using the “Reload Window” command in VSCode to trigger reindexing?
Yes. I was restarting VS code before and tried again with reloading the window this time. I see VS code searching and fining all dependencies except my manually installed one.
Still looking into it. I’m having trouble getting yaml to install on Create-2022.3 in order to verify. I’m using omni.kit.pipapi.install, but it should work the same. You didn’t do anything special?
In regards to .pyd, if there are any .py or .pyi files, it should find those and intellisense should be available for those.
Ok. So, PyYAML did work for you and idk what the yaml package is. :) What happens with pipapi.install() is that it does an import check to see if the package has been installed and to verify that the install worked. When the import name is different from the PyPI name, it will throw an error unless you use the module kwarg: