potiuk opened a new pull request, #26153:
URL: https://github.com/apache/airflow/pull/26153
The conrib modules are carried from Airflow 1.10 and we cannot
remove the classes that were used there without bumping Airlfow
to 3, however we can replace the files with dynamic attribute
retrieval following PEP-562. This way we will have far less number
of files in contrib and users will not get auto-import and
autocomplete when they will be developing their DAGs.
This does not break compatibility but it providers much stronger
signal to the users that they should switch to new classes:
* they will not see the classes in autocomplete and autoimport
any more
* it will seem that the classes are not existing in contrib until
they are used
* if anyone performs static analysis on the DAGs, the analysis
will fail (and this is an intended behaviour)
<!--
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]
