Re: [DISCUSS] AIP-3: Drop Python2 support in Airflow 2.0

This ticket also suggest function that doesn't support Python 3 https://issues.apache.org/jira/browse/AIRFLOW-2243 Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Sunday, February 24, 2019 9:25 PM, Bas Harenslak wrote: > Following the comments to warn users about droppi

Re: [DISCUSS] AIP-3: Drop Python2 support in Airflow 2.0

Following the comments to warn users about dropping Python 2, I went ahead and added the deprecation library to Airflow in this PR: https://github.com/apache/airflow/pull/4763, and added the first @deprecated annotation. I checked a few major packages and all use some self-made annotation for

Re: [DISCUSS] AIP-3: Drop Python2 support in Airflow 2.0

The PR comments say drop hdfs3 and use pyarrow, however this is not implemented yet. > On 17 Feb 2019, at 08:42, zhong jiajie wrote: > > I overlook the PR https://github.com/apache/airflow/pull/3560 still use > **hdfs3** rather than **PyArrow**. So which package we choice finilly? > [https://

答复: [DISCUSS] AIP-3: Drop Python2 support in Airflow 2.0

I overlook the PR https://github.com/apache/airflow/pull/3560 still use **hdfs3** rather than **PyArrow**. So which package we choice finilly? [https://avatars3.githubusercontent.com/u/307739?s=400&v=4] [AIRFLOW-2697] Drop snakebite in favour of hdfs3

Re: [DISCUSS] AIP-3: Drop Python2 support in Airflow 2.0

One blocker is HDFS support. Right now we rely on Snakebite which is Python2 only, so we need to update this as well. There is an open ticket: https://jira.apache.org/jira/browse/AIRFLOW-2697 Op vr 15 feb. 2019 om 07:55 schreef zhong jiajie : > Agree with XD's second idea, we should warn Airflow

Re: [DISCUSS] AIP-3: Drop Python2 support in Airflow 2.0

Agree with XD's second idea, we should warn Airflow users. My two cents: 1. Can we discuss on the timeline for 2.0? Another big change is FAB-UI ONLY, which is already in master branch. Personally I think it’s already worth considering 2.0, unless there is other

Re: [DISCUSS] AIP-3: Drop Python2 support in Airflow 2.0

My two cents: 1. Can we discuss on the timeline for 2.0? Another big change is FAB-UI ONLY, which is already in master branch. Personally I think it’s already worth considering 2.0, unless there is other existing expectation for 2.0. 2. Before we completely drop Python2 support, we can start add

Re: [DISCUSS] AIP-3: Drop Python2 support in Airflow 2.0

I would like to point out that dropping the support for Python 2.7 must take place when releasing the major version. Airflow 1.0 was released on 4 Jun 2015 (3.5+ years ago ),which means that Airflow is trying to maintain compatibility for a long period of time. If we release the next version, I t

[DISCUSS] AIP-3: Drop Python2 support in Airflow 2.0

We talked about this in the past but I'd like to bring it up again with a more concrete proposal. At the time Airflow 2.0 wasn't very concrete, but no