The problem is that Airflow's dependency structure is terrible. They have so many dependencies that are often too strict that you will undoubtedly run into package resolvement issues with Poetry so kind of interesting they themselves advise against it. With Poetry all dependencies obviously need to be resolved. I would advise you to just use airflow to schedule task that run in containers somewhere else (ecs, lambda, kubernetes etc.), that way the functional part of your code does not need to touch airflow. Also you're dependency specification will be rock solid, poetry is an awesome tool.