-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Replace DeprecationWarning with DeprecatedImportWarning 8 files across airflow-core #56836
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
Conversation
c7295f3 to
abe78f8
Compare
amoghrajesh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice thanks @KoviAnusha!
Could you run a quick test by trying to run DAGs with some or all of those imports to see if you can see those errors in the task logs? I am OK to approve once thats done.
|
@amoghrajesh, I have created a sample DAG, and I can see DeprecatedImportWarning in the warnings. Please let me know if this is okay?
|
|
That looks good thanks! |
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 7d02211 v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |

closes: #55889
Replaced DeprecationWarning with DeprecatedImportWarning across airflow-core in the following files
^ 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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.