airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ash Berlin-Taylor <>
Subject Re: [VOTE] Accept AIP-3: Drop support for Python 2
Date Sun, 24 Mar 2019 08:33:08 GMT
+0 (binding)

I am in favour of this (I created the AIP after all!) But note this puts an end to backporting
fixes to 1.10 series, so once we merge this we should release 2.0.0 soon after.


On 23 March 2019 23:19:11 GMT, "Driesprong, Fokko" <> wrote:
>Dear Airflow community,
>This email calls for a vote to accept Airflow Improvement Proposal 3:
>support for Python 2
>The vote will last for at least 1 week until Midnight Sunday 31th of
>and until three +1 (binding) votes have been cast
>This vote is on the proposal itself, not any specific code or pull
>A failed vote does not mean the proposal is rejected, just not accepted
>this time. (To reject a proposal entirely is its own vote)
>This is my +1 (binding) vote.
>Having to support Python 2 and 3 concurrently causes some maintenance
>development burden (which is lessened a bit by six and backports
>significant extra test time on Travis, and more complexity on the CI
>process to also have Python 2 images.
>Python 2 is reaching End of Life in January 1, 2020 and will receive
>updates, even security ones past this date.
>Django dropped support for Python 2 with their 2.0 release in December
>2017, and this proposal has us follow suit. Airflow 2.0 is already a
>major breaking change, so this could be an opportune time to do this.
>is already a significant list of projects which are dropping support
>Furthermore, the community started recently adding types to the code of
>Airflow to help new contributors, and make the code more
>Right now we're limited to setting these types in the comments, to
>Airflow 2.7 compatibility, which is a pity.
>For discussing the proposal in depth, please refer to the Wiki to keep
>the communication in a single place:

  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message