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 have never used Python with Pulumi before, but when I look at the provided example, I nowhere see `import pulumi_kubernetes` in the code. I always see `from pulumi_kubernetes.&lt;subpackage&gt; import &lt;class&gt;`
<https://github.com/pulumi/examples/tree/master/kubernetes-py-guestbook>

Thanks for your help, but I have seen `import pulumi_kubernetes` working before.

However, I am a little bit confused on what exactly happens, when I call `pulumi up` .
1. The pulumi that was installed with brew executes the command and has access to python packages that are in the mac os standard python installation.
2. The pulumi that was installed with brew executes the command and has access to python packages that are in the mac os standard python installation and the packages that are in the activated conda environment.
3. The pulumi from the conda environment is called with all python packages available in the conda environment.
Subsequently, the following questions arise:
• If pulumi is entirely run from packages in virtual environment (conda, venv, …) why `brew install pulumi` at all?
• If pulumi is entirely run from packages in base environment, why use virtual environments?
Reconsidering the questions origin, it’s probably more appropriate in the  <#CDE799L1M|> channel