GitHub user pykenny added a comment to the discussion: Separate Python virtual environments for each DAG(not Task)
Otherwise, [as earlier response](https://github.com/apache/airflow/discussions/40651#discussioncomment-9988010) suggested, one need to tackle with remote executors (Kubernetes or Celery) to deploy remote workers using different Python environments (of course, both requires Airflow to be available worker's runtime). GitHub link: https://github.com/apache/airflow/discussions/40651#discussioncomment-13074555 ---- This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org