-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve modules import in Airflow core by some of them into a type-checking block #33755
Conversation
I think it's ready, I fixed the wrong import in utils.session, and I reverted the change which update the lazy import logic in the models module. I checked the files one by one, and all looks good. |
c6f2a42
to
edc3d76
Compare
This is a huge and potentially conflicting change (thought the conflicts will be easy to solve because those are only import changes. I am a little torn on this one- should we split it inte separate per "package/subpackage" maybe to limit the cherry-picking radius blast ? |
I agree, I had the same concern, but I preferred to hear from the reviewers before making this change. |
6166f8e
to
d9b05da
Compare
I think we can keep the remaining files in a single PR |
LGTM |
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
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.