Thanks for spearheading this, Vincent. Great teamwork, everyone!
Thanks & Regards, Amogh Desai On Tue, Nov 4, 2025 at 3:57 AM Vincent Beck <[email protected]> wrote: > I forgot to mention, I keep rebasing > https://github.com/apache/airflow/pull/56212 which removes the constraint > on sqlalchemy<2 so you can find all the errors I mentioned in my previous > email in this PR's CI. > > On 2025/11/03 22:15:45 Vincent Beck wrote: > > Hi everyone, > > > > A quick status on SQLAlchemy 2 migration: > > > > - From 525 errors in core Airflow we are down to 64. Please look at > https://github.com/apache/airflow/issues/56735 if you are interested > and/or want to help us reach 0 > > - From 193 errors we are down to ... 0. Actually, I am lying, 2 > providers are left but we already have open PR for these 2 so it is only a > matter of reviewing and merging > > - Kubernetes provider: https://github.com/apache/airflow/pull/57563 > > - Databricks provider: https://github.com/apache/airflow/pull/57768 > > - There is one open PR to resolve the 2 errors from devel-common: > https://github.com/apache/airflow/pull/57774 > > - There are still 4 errors in task SDK. Any help is appreciated on that > front :) > > > > But most importantly, huge thanks to all the contributors and reviewers > for their amazing work fixing these static errors — we’re so close to the > finish line! > > > > Vincent > > > > On 2025/10/17 07:17:31 Pavankumar Gopidesu wrote: > > > Thanks vincet, finally :) > > > > > > Pavan > > > > > > On Fri, 17 Oct 2025 at 07:18, Amogh Desai <[email protected]> > wrote: > > > > > > > Thanks for spearheading this, Vincent. > > > > > > > > Exciting to see it finally happening. > > > > > > > > If you / anyone gets hold of a good prompt for AI, do share it on the > > > > Github issues > > > > so that others can benefit from it as well. > > > > > > > > Thanks & Regards, > > > > Amogh Desai > > > > > > > > > > > > On Thu, Oct 16, 2025 at 10:59 PM Beck, Vincent <[email protected]> > > > > wrote: > > > > > > > > > Hi everyone, > > > > > > > > > > We are getting close to be able to migrate to SQL2. Currently we > are > > > > still > > > > > limiting sqlalchemy to version 1 ( > > > > > > > > > > https://github.com/apache/airflow/blob/main/providers/fab/pyproject.toml#L80 > > > > ) > > > > > because our type annotations across the codebase is not compatible > with > > > > > SQLA2. When SQLA2 is enabled, mypy gets very angry and report a > lot of > > > > > static errors as you can see in > > > > > https://github.com/apache/airflow/pull/56212. > > > > > > > > > > The idea is, to migrate to SQLA2 but also to improve type safety > and code > > > > > quality, solve all these static errors. There are currently: > > > > > > > > > > * 525 errors in core Airflow > > > > > * 193 errors in providers > > > > > * 4 errors in task SDK > > > > > * 2 errors in devel-common > > > > > > > > > > Given the number of errors, I need you 😊 By dividing and > conquering, we > > > > > can easily and quickly solve these errors. To make it easy I > created 2 > > > > > issues, one tracking errors in core Airflow, one tracking errors in > > > > > providers. No need to create issue for Task SDK and devel-common, > there > > > > are > > > > > just a few. > > > > > > > > > > > > > > > * Issue tracking errors in core Airflow: > > > > > https://github.com/apache/airflow/issues/56735 > > > > > * Issue tracking errors in providers: > > > > > https://github.com/apache/airflow/issues/56738 > > > > > > > > > > In these issues you can find steps on how to generate these > errors. If > > > > you > > > > > are interested to help Airflow using SQLA2, then please feel free > to > > > > > pick-up some files/directories as part of these issues and resolve > the > > > > > errors in these files. Solving these static errors is not > complicated, > > > > > there are just a lot 😊 > > > > > > > > > > Thank you for your help! > > > > > Vincent > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
