potiuk commented on a change in pull request #6596: [AIRFLOW-6004] Untangle 
Executors class to avoid cyclic imports
URL: https://github.com/apache/airflow/pull/6596#discussion_r353155596
 
 

 ##########
 File path: UPDATING.md
 ##########
 @@ -41,6 +41,30 @@ assists users migrating to a new version.
 
 ## Airflow Master
 
+### Changes to airflow package imports
+
+Importing `executor`, `hooks`, `macros`, `operators`, `sensors` packages no
+longer works indirectly via airflow package. For example this will not work:
+
+```python
+import airflow
+
+operator = airflow.operators.BashOperator(...)
 
 Review comment:
   I do not think there was a warning. I think it's not really possible (or 
easy and reliably) to have a warning depending on how you import class if it's 
location does not change. I don't think there is enough information on how the 
import happened when the __init__.py is executed for the package or when you 
reach the class.

----------------------------------------------------------------
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:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to