Skip to content

Conversation

@tgrandje
Copy link


As discussed in #46266 there are (and will be more) usecases for sqlalchemy>0.2.0 usage. As far as I know, this will stay there untill Airflow 3 is released. Until then, (I think) there is a good point for documenting on how to deal with this, even if this is not intended behaviour: pandas for instance cannot work with Airflow as of yet.

The current PR :

  • adds a general warning on using dependencies in a virtualenv which are not compatible with airflow (this subject was not documented yet I think)
  • adds a note in the virtualenv tutorial listing the known side effects to using sqlalchemy>0.2.0.

@tgrandje
Copy link
Author

This is a followup for #47914

@potiuk
Copy link
Member

potiuk commented Mar 30, 2025

We are working to have airflow 2-10-test branch green again , so this one is likely to fail for now - #48404

@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale Stale PRs per the .github/workflows/stale.yml policy file label Jun 14, 2025
@github-actions github-actions bot closed this Jun 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind:documentation stale Stale PRs per the .github/workflows/stale.yml policy file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants