Add compat shim for SQLAlchemy to avoid warnings #21959
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SQLALchemy 1.4 is introducing a ton of deprecation warnings to our code base. They need to be fixed eventually if we want to support SQLALchemy 2.0, so this introduce shims to ease the migration in the future, while squelching the warnings in the mean time.
This cleans up 76 deprecation warnings emitted by
test_dag_serialization.py
, from 827 to 743. Yeah that’s still a ton of warnings, although a good portion are fromdays_ago
usages in our example DAGs.