-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Use Python 3.9 as target version for Ruff & Black rules #44298
Conversation
eafce90
to
83f26a2
Compare
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.
Interesting. How can it be that I over-looked the changes in the first commit when removing Python 3.9 support?
a9100f8
to
bb118b6
Compare
Nice - but seems there are still some troubles with collection changes. BTW. I would like - before merge and when green re-run it locally and reapply ruff auto-changes - to see if I come up with small set of reviewable changes (aka - reproducibility check :) |
Since we dropped support of Python 3.8 (after it reach EOL), we missed changing rules for black & ruff.
bb118b6
to
254359c
Compare
Done, rebased, ran ruff, force pushed locally |
You already had to many changes to handle :) |
All good man |
Since we dropped support of Python 3.8 (after it reach EOL), we missed changing rules for black & ruff.
For reviewers: easier to just review first commit, second commit is mostly autogen code
^ 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.