I am not sure why it works in airflow (perhaps dags are parsed in distinct processes???). But, thinking of how you might fix this.... it seems you are doing relative imports. Maybe if you stop doing that, that would be enough. So instead of importing `from config import value` you could do `from dags.my_dir1.my_dir2.config import value`. Then you wouldn't need to muck with the python path either.
- How does DAG loading isolation work? Chris Redekop
- Re: How does DAG loading isolation work? Daniel Standish
- Re: How does DAG loading isolation work? Jarek Potiuk
- Re: How does DAG loading isolation work? Chris Redekop
