GitHub user potiuk edited a comment on the discussion: Constraints in 3.0.3 have incompatible combination of pandas & sqlalchemy
Thanks @jabbera for following up with this one despite me being hesitant. It turned out that that our pandas requirement for postgres and common.sql providers just missed those extras - that was the root of the problem. Yeah. The pr worked. You will see in "source providers" constraints in main that pandas is now 2.1.4. https://github.com/apache/airflow/blob/constraints-main/constraints-source-providers-3.11.txt When the next wave of providers is released (next week) also "constraints-3.11.txt" will be updated (those constraints are build automatically based on the released providers in PyPI (actually in main it should get updated as soon as RCs are released - because our constraint building mechanism includes also RC candidates as of few months). Then, when we release 3.0.4 it will use the released providers, and then it should get update for 3.0.4 constraints. Sometimes we fix constraints for past released versions (last time yesterday) - https://airflow.apache.org/docs/docker-stack/changelog.html#changes-after-publishing-the-images -> but we only do it for **really** critical changes that affect many users, in this case I think the issue is really affecting small number of users who want to use from_df/to_df and there is an existing workaround (just downgrade pandas to 2.1.4) so I do not see a need to regenerate the images and update constraints manually. Unless there are many people complaining and some other reasons why this is problematic to have pandas 2.2.3 in constraints. GitHub link: https://github.com/apache/airflow/discussions/53392#discussioncomment-13822862 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
