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

Posted to commits@airflow.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2016/06/29 03:20:45 UTC

[jira] [Closed] (AIRFLOW-285) Update remaining imports to use 2.0 style

     [ https://issues.apache.org/jira/browse/AIRFLOW-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Riccomini closed AIRFLOW-285.
-----------------------------------
    Resolution: Fixed

> Update remaining imports to use 2.0 style
> -----------------------------------------
>
>                 Key: AIRFLOW-285
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-285
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: core
>    Affects Versions: Airflow 1.7.1.3
>            Reporter: Chris Riccomini
>            Assignee: Chris Riccomini
>             Fix For: Airflow 1.8
>
>
> As part of AIRFLOW-200, I noticed that not all imports were updated in AIRFLOW-31. Some are still using old style imports (e.g. {{from airflow.operators import BashOperator}}). This causes a problem with my AIRFLOW-200 patch, as it assumes if new style imports are used, they'll be used for all hooks/operators.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)