GitHub user smktpd created a discussion: Why do pip packages apache-airflow-providers-* and apache-airflow have cyclic dependencies?
I use `pipdeptree` to watch dependency graphs of pip packages in my images. With image docker.io/apache/airflow:2.11.0-python3.12 it notifies me of such cyclic dependencies: ``` Warning!!! Cyclic dependencies found: * apache-airflow-providers-common-compat => apache-airflow => apache-airflow-providers-common-compat * apache-airflow-providers-common-io => apache-airflow => apache-airflow-providers-common-io * apache-airflow-providers-common-sql => apache-airflow => apache-airflow-providers-common-sql * apache-airflow-providers-fab => apache-airflow-providers-common-compat => apache-airflow => apache-airflow-providers-fab * apache-airflow-providers-ftp => apache-airflow => apache-airflow-providers-ftp * apache-airflow-providers-http => apache-airflow => apache-airflow-providers-http * apache-airflow-providers-imap => apache-airflow => apache-airflow-providers-imap * apache-airflow-providers-smtp => apache-airflow => apache-airflow-providers-smtp * apache-airflow-providers-sqlite => apache-airflow => apache-airflow-providers-sqlite * apache-airflow => apache-airflow-providers-common-compat => apache-airflow ``` I understand that this got to be non-critical, but still feels off, so I wonder why they are made so. GitHub link: https://github.com/apache/airflow/discussions/61474 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
