-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SNOW-396922: Snowflake patch change from 1.2.4 to 1.2.5 introduces a hard dependency on sqlalchemy>=1.4.0 #234
Comments
We are in the process of releasing the fix you provided in order to get this addressed as quickly as possible. Our team is reviewing how we can avoid this in the future through additional test cases and we will also review if a longer term fix is needed. |
Re-opening this issue to keep it visible to anyone that runs into the following error in the next while:
Solutions:
|
Is the second option available? Appears the latest version is 1.2.5? |
@jimkim-tc I will update here once the next version is released , likely Monday. |
Released new version 1.3.1 for Snowflake SqlAlchemy which has the fix. Let us know for any issues. |
@sfc-gh-abhatnagar This is still a problem. In the Apache Airflow project, we don't support SQLAlchemy 1.4, as Flask-AppBuilder dependency doesn't support SQlAlchemy 1.4 yet. Flask-App-Builder has a corresponding entry in # SQLAlchemy 1.4.0 breaks flask-sqlalchemy and sqlalchemy-utils
"SQLAlchemy<1.4.0", Here is definition requirement of flask-appbuilder>=3.3.2, <4.0.0 In other words, Apache Airflow requires SQLAlchemy 1.3+, <1.4. snowflake = [
'snowflake-connector-python>=2.4.1',
'snowflake-sqlalchemy>=1.1.0',
] Unfortunately, these constraints is not sufficient as pip installs snowflake = [
'snowflake-connector-python>=2.4.1',
'snowflake-sqlalchemy>=1.1.0',
# The snowflake-alchemy 1.2.5 introduces a hard dependency on sqlalchemy>=1.4.0, but they didn't define
# this requirements in setup.py, so pip cannot figure out the correct set of dependencies.
# See: https://github.com/snowflakedb/snowflake-sqlalchemy/issues/234
'snowflake-sqlalchemy>=1.1.0,!=1.2.5',
] Could you mark the
(source: https://pypi.org/help/#yanked) |
For reference: SNOW-518532 - Ticket about marking one release as yanked. |
We have marked |
This is a potential breaking change that is not captured in setup.py and should not be part of a patch version. More context in this PR which ideally should not be the solution.
The text was updated successfully, but these errors were encountered: