No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

image.png

I think it’s to do with how the language server in VSCode sees the SDK.

I’m no expert in Python but I use option 1 all the time and I’ve found it useful to activate the virtual environment (so `source venv/bin/activate`) and then open VSCode from the command line.

Or you can open VSCode and then activate the virtual environment. Otherwise VSCode will struggle to see the SDK

thanks <@U01FB0HRB2Q>, venv is not a problem here, otherwise vscode won’t see any pulumi imports whatsoever
it is just that with option 1 it doesn’t show the descriptions.

This is almost certainly related how the sdk for py is generated, but I was curious if others find it the same