Re export AirflowPlugin to fix mypy errors in plugins

[amoghrajesh]

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

Custom plugins written with AirflowPlugin face mypy errors:

mypackage/src/mypackage/plugins/mymodule.py:27: error: Module "airflow.plugins_manager" does not explicitly export attribute "AirflowPlugin"  [attr-defined]

The best way to do this is to re export them from the packages that are public API for it.

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[potiuk]

Interesting - is that enough ? That does not sound like this should have such effect ? Is it A Typing/MyPy specific thing that you have to do 'X as X' to be visible in MyPy as explicitly exposed ?

[potiuk]

Ah TIL

[potiuk]

import - In Python, what's the purpose of giving an alias with the same name as the imported lib? - Stack Overflow https://share.google/7zvymClHaTqQuUHiA

[potiuk]

I personally prefer all but this works too :)

[amoghrajesh]

import - In Python, what's the purpose of giving an alias with the same name as the imported lib? - Stack Overflow https://share.google/7zvymClHaTqQuUHiA

Yeah :D

I do not have a strong preference but I like re importing with same name, makes it a bit explicit / more "re export" like.

[jscheffl]

Cool, thanks for the quick fix!

[jscheffl]

Can we get this into 3.2.1?

[potiuk]

Can we get this into 3.2.1?

I believe everything in v3-2-test goes to 3.2.1 now :)