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 adding warning/reminder mentioning that it’s stronly recommended to use py3 & py2 drooping can happen “at any time” for Airflow (we can add these warnings in 1.10.3?) XD On Thu, Feb 14, 2019 at 18:42 Ash Berlin-Taylor <a...@apache.org> wrote: > We talked about this in the past < > http://mail-archives.apache.org/mod_mbox/airflow-dev/201808.mbox/%3CCAK%2Be0oujpY1A0mD0G775CmmRneVDjQMTi99aqK%2BA_C07ZW8ySA%40mail.gmail.com%3E> > 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 now with a lot of > otherwise breaking changes already on master how about we use that time to > also drop support for Py2? > > (Reminder: Python 2 is reaching End of Life in January 1, 2020 and will > receive zero updates, even security ones past this date. At least not by > the Python team. I imagine RedHat will still be running Python 2.6 in 2120 > ;) ) > > -ash
