GitHub user potiuk closed the discussion with a comment: Why do pip packages apache-airflow-providers-* and apache-airflow have cyclic dependencies?
Becaue your solution will not work outside of docker - 30% of our users do not use any containerisation - so any solutions based on docker will not help those users, so proposing it makes no sense. See https://airflow.apache.org/blog/airflow-survey-2025/ Cyclic dependencies (for now) is needed until we finish task-isolation work, Currently providers depend on `apache-airflow` but in airflow 3.2 or 3.3 - they are supposed to only depend on a new `task-sdk` distribution rather than on `apache-airflow`. Removing those cyclic dependencies was one of the goals of https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-72+Task+Execution+Interface+aka+Task+SDK which is still not completed. You can read more about history and reasoning there. GitHub link: https://github.com/apache/airflow/discussions/61474#discussioncomment-15829350 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
