I have the following project structure:

.
├── flow_definitions
│   ├── __init__.py
│   ├── masterdata
│   │   ├── deployment.py
│   │   ├── extract_data.py
│   │   └── __init__.py
│   ├── classification
│   │   ├── deployment.py
│   │   ├── __init__.py
│   │   └── preprocessing.py
│   └── utils
│       ├── date_utils.py
│       ├── __init__.py
├── README.md
├── requirements.txt
└── setup.py

In

classification/preprocessing.py

, I am doing a sibling import as follows:

from flows.flow_definitions.utils.date_utils import parse_date

However, this fails:

ModuleNotFoundError: No module named 'flows'

since it seemingly can't find my parent module (

.

). Strictly speaking, this is a Python problem and not a prefect issue. However, I can't seem to find an example detailing this kind of approach. I thought that maybe the Deployment

path

parameter might have something to do with this scenario, but it seems that's not the case. So, is there an example of a project using common functionality? Do I have to install my

utils

module, or is there another preferred way to get this to work in my flows?

Actually, the script entrypoint code may be off, can't remember how I used to do it. Typically you want them to be purely import, so try to make that work.