o-nikolas opened a new pull request, #29257: URL: https://github.com/apache/airflow/pull/29257
The `airflow.configuration.conf` object is initialized and validated as a consequence of the first time it is imported. This currently happens to be when it is imported in the `airflow.settings` module. However, that causes issues because those two modules are tightly coupled so it frequently happens that modifications to `conf` code creates import cycles since, as mentioned above, most of that code is executed downstream from its initial import in `airflow.settings` module. This change adds an **intentional** import of `airlfow.configuration` early (in `airflow.__init__`) to specifically trigger the initialization and validation of `conf` before `airflow.settings`. This allows _most_ `conf` code to run without worry of causing import cycles with `airflow.settings`. <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of an existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
