You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/12/08 21:45:59 UTC

[GitHub] [airflow] turbaszek edited a comment on issue #12895: from airflow.operators.python import PythonOperator does not work

turbaszek edited a comment on issue #12895:
URL: https://github.com/apache/airflow/issues/12895#issuecomment-741082034


   Using old path will raise a warning. I think that current suggestion given by airflow upgrade check should be understood as "if you want to make your DAG fully compatible with Airflow 2.0 and limit number of warnings you get change the import path A to import path B". 
   
   I can be wrong, be the check was to help migrate DAGs not to make them 1.10 and 2.0 compatible. Otherwise we have to redesign the checks. If we think that current behaviour  is unclear then we should improve either messages or docs (or both).


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org