Yeah. This is why we need to do it one-by-one and make individual decisions on how to approach this :). Nice thing is that once we complete task isolation and task-sdk will not have sqlalchemy dependencies, the way how we do testing with uv sync will catch those kind of errors automatically - because sqlalchemy will not be installed during tests if not declared - so it means that we do not have to even have any prek hooks to check future changes.
On Tue, Dec 30, 2025 at 7:02 AM Amogh Desai <[email protected]> wrote: > Good catch! > > Strange to see that some of those providers need sqla for some feature of > their own! > > Thanks & Regards, > Amogh Desai > > > On Tue, Dec 30, 2025 at 1:19 AM Jarek Potiuk <[email protected]> wrote: > > > While reviewing a hive PR I realized that some of our providers have an > > implicit sqlalchemy dependency - I think all those providers do not have > > sqlalchemy declared as one because currently sqlalchemy is provided by > > "airflow-core" - but when we complete task isolation, task-sdk will not > > have sqlalchemy as dependency, so those providers should have it > declared - > > most of them as optional "extra" dependency, some of them as "required" > > (for the common.sql and related, sqlalchemy should be purely optional). > > > > I created issue https://github.com/apache/airflow/issues/59895 -> as > "good > > first issue" and created sub-issues for each provider that uses > sqlalchemy > > now. > > > > Feel free to grab them. > > > > J. > > >
