GitHub user potiuk closed the discussion with a comment: There is no pip package `apache-airflow-providers-standard` in the official docker image. Why?
> So if that package is for Airflow 2.11.0 and provides PythonOperator - it's > pretty logical to think that Airflow 2.11.0 shouldn't have PythonOperator > without 'standard' provider's pip package installed. It is not installed in > your image, yet somehow the operator is available there, which is confusing. No. It has nothing to do with logic - it's more jumping to conclusion without understanding the context. See https://airflow.apache.org/docs/apache-airflow/stable/installation/upgrading_to_airflow3.html#step-4-install-the-standard-provider Allowing standard provider is to ease migration. See upgrading docs from Airflow 2 to 3. T he presence of old "standard" operators in 2.11 is needed for backwards compatibiliity. Removing them would violate SemVer. So if you want to prepare your Dags for migration to 3 you install standard provider (additionally to what you have in 2.11) and then you can convert your Dags to use the standard provider before you attempt to migrate. Thus avoiding big bang. User needs to take deliberate decision on installing standard provider manually if they want to do it. Having it installed and having two implementations of standard providers in two places without users deliberately asking for that would be far more confusing. GitHub link: https://github.com/apache/airflow/discussions/61473#discussioncomment-15829398 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
