FYI who was not on the dev call today.
We discussed about this but no majority was there to drop support for
Python 3.9 early. Rather the migration to SQLalchemy2 would be
post-poned to Airflow 3.2 or so as:
- The FAB dependency to 5.0 might need to be integrated first - and
SQLalchemy is no
I would also favor dropping python 3.9 it would make a lot of code cleaner
and easier to manage.
Sure let's discuss in the dev call.
- Avi
On Thu, May 8, 2025 at 5:47 AM Amogh Desai wrote:
> I would also be for bumping the minimum python version to 3.9+ for Airflow
> 3.1 unless
> there is some
I would also be for bumping the minimum python version to 3.9+ for Airflow
3.1 unless
there is some objection to this one.
Maybe we should add this as a discussion item for the Airflow dev call?
Thanks & Regards,
Amogh Desai
On Thu, May 8, 2025 at 11:09 AM Jarek Potiuk wrote:
> I would be for
I would be for it if that makes things easier. We could drop Python 3.9 for
airflow 3.1+
On Wed, May 7, 2025 at 10:01 PM Jens Scheffler
wrote:
> Hi Avi, all,
>
> we had a bit of a discussion about this and don't know if this is very
> controversal... but: Python 3.9 will run out of support in Se
Hi Avi, all,
we had a bit of a discussion about this and don't know if this is very
controversal... but: Python 3.9 will run out of support in September.
How about if we drop support early in 3.1 so that we migrate main to
3.10 and by this remove the deadlock?
Jens
On 07.05.25 16:48, Abhish
Hi All,
I've hit a little deadlock.
We want to use SQLAlchemy 2.x ORM typing (Mapped[...] =
mapped_column(...)) with
PEP 604 union types (int | None) in model annotations and must support
Python 3.9 (which does not support int | None at runtime).
We do not want to use Optional[...] (ruff UP007 i
