Re: Python 3.6 Support for Airflow 1.10.0

Strong +1 for keeping 2.7 for now. We've 30+ big and small enterprises running Airflow as a service on our platform and they all are on py 2.7 for now. Soon we are adding support for py 3.5 as well, but still, not everyone gonna switch to that immediately. So IMO we should keep the support of py

Re: Python 3.6 Support for Airflow 1.10.0

+1 for keeping 2.7 as well. Lyft runs airflow on 2.7 internally. On Tue, Aug 28, 2018 at 1:12 PM, Feng Lu wrote: > +1 for keeping 2.7 as long as we can so people have time to plan and > migrate away from it. > > On Tue, Aug 28, 2018, 10:35 Arthur Wiedmer > wrote: > > > Given that Python 2.7

Re: Python 3.6 Support for Airflow 1.10.0

+1 for keeping 2.7 as long as we can so people have time to plan and migrate away from it. On Tue, Aug 28, 2018, 10:35 Arthur Wiedmer wrote: > Given that Python 2.7 EOL is slated for January 1st 2020, we should > probably ensure that the early releases of 2019 are still 2.7 compatible. > >

Re: Python 3.6 Support for Airflow 1.10.0

Given that Python 2.7 EOL is slated for January 1st 2020, we should probably ensure that the early releases of 2019 are still 2.7 compatible. Beyond this, I think we can also be responsible security wise and help nudge people towards 3. Best, Arthur On Tue, Aug 28, 2018 at 10:28 AM Bolke de

Re: Python 3.6 Support for Airflow 1.10.0

Let’s not drop 2.7 too quickly but maybe mark it deprecated. I’m pretty sure Airbnb still runs on 2.7. Also RedHat does not deliver python 3 in its enterprise edition yet by default so it will put enterprise users in a bit of an awkward spot. B. Verstuurd vanaf mijn iPad > Op 28 aug. 2018 om

Re: Python 3.6 Support for Airflow 1.10.0

I'm +1 on going to 3.7 -- I'm running 3.6 myself. Regarding dropping Python2 support, with almost 200 companies using Airflow, I'd want to be very careful that we don't put any of them at a disadvantage. For example, my former employer (a small startup) is running on Python2 -- after I left, they

Re: Python 3.6 Support for Airflow 1.10.0

We should definitely support 3.7. I left comments on the PR @tedmiston regarding the same. Python 2.7 will be dropped in 2020, so I guess we should start planning about it. Not really 100% sure though that we should drop it in Airflow 2.0 On 28/08/2018, 17:08, "Taylor Edmiston" wrote:

Re: Python 3.6 Support for Airflow 1.10.0

I am onboard with dropping Python 2.x support. Django officially dropped Python 2.x support with their 2.0 release since December 2017. *Taylor Edmiston* Blog | CV | LinkedIn | AngelList

Re: Python 3.6 Support for Airflow 1.10.0

Supporting 3.7 is absolutely something we should do - it just got released while we were already mid-way through the release process of 1.10 and didn't want the scope creep. I'm happy to release a 1.10.1 that supports Py 3.7. The only issue I've seen so far is around the use of `async` as a

Re: Python 3.6 Support for Airflow 1.10.0

We are also running on 3.6 for some time. I put a quick branch together adding / upgrading to 3.6 in all of the places. CI is still running so I may expect some test failures but hopefully nothing major. I would be happy to merge this into Kaxil's current #3815 or as a follow-on PR. I'll paste

Re: Python 3.6 Support for Airflow 1.10.0

fwiw, we run Airflow on Python 3.6. On Tue, Aug 28, 2018 at 8:30 AM Naik Kaxil wrote: > To provide more context to the issue: > > > > PyPI shows that Airflow is supported on Py2.7, 3.4 and 3.5 : > https://pypi.org/project/apache-airflow/ > > > > This is picked from setup.py: > > >

Re: Python 3.6 Support for Airflow 1.10.0

To provide more context to the issue: PyPI shows that Airflow is supported on Py2.7, 3.4 and 3.5 : https://pypi.org/project/apache-airflow/ This is picked from setup.py: https://github.com/apache/incubator-airflow/blob/26e0d449737e8671000f671d820a9537f23f345a/setup.py#L367 So, should we