Using bind mounts when developing locally


I have a specific usecase where I want to develop a Python package locally that I want to be able to work well with astronomer. I am also working on Windows. I’d like to install the package with the -e flag.

i.e. I have a Python package living in C:\dev\my_package. I have an astronomer project in C:\dev\astro. My initial thought would be to just have this line in my C:\dev\astro\requirements.txt: -e ..\\my_package. This obviously didn’t work. Then I thought I might add a docker-compose.override.yml like so to bind mount the files to the container:

version: "2"
      - C:\dev\my_package:/usr/local/airflow/my_package:ro
      - C:\dev\my_package:/usr/local/airflow/my_package:ro

and then have my requirements.txt like so to install the package:

-e /usr/local/airflow/my_package

But this also does not work, giving the same error:

ERROR: /usr/local/airflow/my_package is not a valid editable requirement. It should either be a path to a local project or a VCS URL (beginning with svn+, git+, hg+, or bzr+).

Is there a good way to achieve my desired result of developing a Python package for use in astronomer locally?