This message was deleted.

sparse-intern-71089

03/16/2022, 5:28 PM

This message was deleted.

purple-plumber-90981

03/17/2022, 3:28 AM

this is a core python concept, not a pulumi specific thing... have a read of

<https://chrisyeh96.github.io/2017/08/08/definitive-guide-python-imports.html#all-about-__init__py>

average-article-76176

03/17/2022, 4:24 PM

Yeah, I understand how init files work, it's just that if I leave them empty Pulumi is not importing the rest of the project, but looks like it's something I'm doing wrong. The answer here pointed to a potential solution. Thank you!

great-sunset-355

03/18/2022, 10:45 AM

This is more about PYTHONPATH it's the same problem as in AWS Lambda. Where the PYTHONPATH starts from

__main__.py

In this case

__main__.py

can import from

python_package_in_path

Copy code

pulumi_project/
  __main__.py
  python_package_in_path/
     __init__.py

but in this case, you cannot because

__main__.py

cannot see the sibling directory.

Copy code

pulumi_project/
  __main__.py

python_package_not_in_path/
     __init__.py

So you need a way to get

python_package_not_in_path

in PYTHONPATH (aka

sys.path

)

average-article-76176

03/18/2022, 5:40 PM

Tx, I'll give this a try.

Open in Slack

Previous Next

Pulumi Community

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.