[DISCUSS] Preparing for dropping Python 3.7 support

[Jarek Potiuk <ja...@potiuk.com>]

Hello everyone.

Just for everyone to be aware - Python 3.7 life is about to end in ~ 2
months.

I prepared a (draft) PR to drop Python 3.7 support:
https://github.com/apache/airflow/pull/30963 to see what it means and I got
it to a green state rather quickly. I will keep rebasing it (the changes
are rather automated and should be easy to keep up) but you can also see
what kind of  changes dropping Python 3.7 support involves (hint - dropping
some compat code, mostly around async testing).

If you want to review it and make comments - feel free - we have time to
iterate on it

The cut-off date is 27 Jun 2023 - this is when EOL for Python support ends
- it's ~2 months away and I plan - according to our policies - to merge it
right after.

It means that if we do not release Airflow 2.7.0 in the next 2 months (we
likely won't), Airflow 2.7.0 will be released with Python 3.8+ support only
(and all providers released after that will also be Python 3.8+ only). The
default docker image pushed for Airflow 2.7.0 will become Python 3.8+ as
well.

There are no changes for Airflow 2.6 -> the bug-fixes in 2.6 will continue
using 3.7 and default image for all Airflow 2.6.* versions will be Python
3.7.

Side comment - Cannot wait to be able to use the Walrus operator in
Airflow finally :).

J.

Re: [DISCUSS] Preparing for dropping Python 3.7 support

["Ferruzzi, Dennis" <fe...@amazon.com.INVALID>]

I am the walrus!  :=

Looking forward to it, thanks for the update.


 - ferruzzi


________________________________
From: Kaxil Naik <ka...@gmail.com>
Sent: Thursday, May 4, 2023 5:40 PM
To: dev@airflow.apache.org
Subject: RE: [EXTERNAL][DISCUSS] Preparing for dropping Python 3.7 support

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.



Let’s do it 🚀

On Mon, 1 May 2023 at 20:16, Jarek Potiuk <ja...@potiuk.com> wrote:

> Just as a heads up as well - it's quite likely we will (finally) get Python
> 3.11 support before that as well. We need two things (likely) for it:
>
> * Apache Beam 2.47 release with protobuf4 support ahttps://
> pypi.org/project/apache-beam/2.47.0rc1/ (RC1 has been cancelled last
> Friday
> due to limiting protobuf too much (some users of beam still need protobuf3)
> * Following that one upgrade to all dependencies of google: which is only
> waiting for the beam upgrade to get through final testing and merging
> https://github.com/apache/airflow/pull/30067
>
> Once the two are merged, I think we will finally be able to release Python
> 3.11 in main and subsequently Airflow 2.7 will likely support 3.8 - 3.11.
> We might even be able to get 3.11 support to one of the 2.6.* actually.
>
>
> On Mon, May 1, 2023 at 9:08 PM Daniel Standish
> <da...@astronomer.io.invalid> wrote:
>
> > Thanks for the heads up about the timing re 2.7 @Jarek.
> >
> > I too am eager for the walrus operator.
> >
>

Re: [DISCUSS] Preparing for dropping Python 3.7 support

[Kaxil Naik <ka...@gmail.com>]

Let’s do it 🚀

On Mon, 1 May 2023 at 20:16, Jarek Potiuk <ja...@potiuk.com> wrote:

> Just as a heads up as well - it's quite likely we will (finally) get Python
> 3.11 support before that as well. We need two things (likely) for it:
>
> * Apache Beam 2.47 release with protobuf4 support ahttps://
> pypi.org/project/apache-beam/2.47.0rc1/ (RC1 has been cancelled last
> Friday
> due to limiting protobuf too much (some users of beam still need protobuf3)
> * Following that one upgrade to all dependencies of google: which is only
> waiting for the beam upgrade to get through final testing and merging
> https://github.com/apache/airflow/pull/30067
>
> Once the two are merged, I think we will finally be able to release Python
> 3.11 in main and subsequently Airflow 2.7 will likely support 3.8 - 3.11.
> We might even be able to get 3.11 support to one of the 2.6.* actually.
>
>
> On Mon, May 1, 2023 at 9:08 PM Daniel Standish
> <da...@astronomer.io.invalid> wrote:
>
> > Thanks for the heads up about the timing re 2.7 @Jarek.
> >
> > I too am eager for the walrus operator.
> >
>

Re: [DISCUSS] Preparing for dropping Python 3.7 support

[Jarek Potiuk <ja...@potiuk.com>]

Just as a heads up as well - it's quite likely we will (finally) get Python
3.11 support before that as well. We need two things (likely) for it:

* Apache Beam 2.47 release with protobuf4 support ahttps://
pypi.org/project/apache-beam/2.47.0rc1/ (RC1 has been cancelled last Friday
due to limiting protobuf too much (some users of beam still need protobuf3)
* Following that one upgrade to all dependencies of google: which is only
waiting for the beam upgrade to get through final testing and merging
https://github.com/apache/airflow/pull/30067

Once the two are merged, I think we will finally be able to release Python
3.11 in main and subsequently Airflow 2.7 will likely support 3.8 - 3.11.
We might even be able to get 3.11 support to one of the 2.6.* actually.


On Mon, May 1, 2023 at 9:08 PM Daniel Standish
<da...@astronomer.io.invalid> wrote:

> Thanks for the heads up about the timing re 2.7 @Jarek.
>
> I too am eager for the walrus operator.
>

Re: [DISCUSS] Preparing for dropping Python 3.7 support

[Daniel Standish <da...@astronomer.io.INVALID>]

Thanks for the heads up about the timing re 2.7 @Jarek.

I too am eager for the walrus operator.