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

This is known issue (it somewhere in pulumi github)
Afaik VSCode worked "okay-ish"
You just need to select the correct interpreter.

If you have setup new pulumi project it also created a VENV so you need to point VSCode to that

Also, it's worth checking into and using Pipenv if you haven't already. It's how we manage all our dependencies for the Pulumi Python implementation.

```[[source]]
name = "pypi"
url = "<https://pypi.org/simple>"
verify_ssl = true

[dev-packages]
black = "&gt;=20.8b0"
debugpy = "*"
flake8 = "*"
pyls-black = "*"
python-language-server = "*"
rope = "*"

[packages]
pulumi = "&lt;4.0.0,&gt;=3.3.0"
pulumi-kubernetes = "&lt;4.0.0,&gt;=3.2.0"
pulumi-vault = "&lt;5.0.0,&gt;=4.0.1"
pulumi-aws = "&lt;5.0.0,&gt;=4.5.1"
pulumi-fastly = "&lt;4.0.0,&gt;=3.1.0"
pulumi-random = "&lt;5.0.0,&gt;=4.1.1"
pulumi-&lt;ORG&gt;-lib = { path = "./pulumi-&lt;ORG&gt;-lib", editable = true }
jinja2 = "*"
boto3 = "*"

[requires]
python_version = "3.8" # Aligns with the version in the official Docker image we base off of.

[pipenv]
allow_prereleases = true```


VScode seems to detect pipenv's presence and subsequently you can pick an interpreter (the one for the pipenv/venv) for the project.