Document working with "sqlalchemy>0.2.0" in virtualenvs and the induced side-effects#48229
Closed
tgrandje wants to merge 1 commit intoapache:v2-10-testfrom
Closed
Document working with "sqlalchemy>0.2.0" in virtualenvs and the induced side-effects#48229tgrandje wants to merge 1 commit intoapache:v2-10-testfrom
tgrandje wants to merge 1 commit intoapache:v2-10-testfrom
Conversation
Author
|
This is a followup for #47914 |
Member
|
We are working to have airflow 2-10-test branch green again , so this one is likely to fail for now - #48404 |
|
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As discussed in #46266 there are (and will be more) usecases for
sqlalchemy>0.2.0usage. 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:pandasfor instance cannot work with Airflow as of yet.The current PR :