My team is considering switching to the composer-dev tool for local development, but there's one thing we have to find a solution for. In our current set-up we run Airflow locally. In some cases our dags need to import code that's neither in the dags folder nor in any PyPi packages. This code is in other folders of our repository and we install them as editable packages, e.g. pip install -e ../../../my-package. This is convenient because any changes we do in those packages are instantly picked-up by Airflow.
Is there any way of handling this case with the composer-dev tool?
Hi!
My team is considering switching to the composer-dev tool for local development, but there's one thing we have to find a solution for. In our current set-up we run Airflow locally. In some cases our dags need to import code that's neither in the dags folder nor in any PyPi packages. This code is in other folders of our repository and we install them as editable packages, e.g.
pip install -e ../../../my-package
. This is convenient because any changes we do in those packages are instantly picked-up by Airflow.Is there any way of handling this case with the composer-dev tool?