-
Notifications
You must be signed in to change notification settings - Fork 321
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
Import broken by sqlalchemy 1.4.0 #505
Comments
👍 same error |
Same issue, error with importing '_ColumnEntity'
|
Can you guys make a quick fix by adding requirement version < 1.4.0? Otherwise if people start doing it they might get stuck with old sqlalchemy |
Duplicate of #474 |
|
The latest 1.4.0 release breaks sqlalchemy-utils. See: kvesteri/sqlalchemy-utils#505
There is another problem:
This is because of this commit in |
* Issue caused by kvesteri/sqlalchemy-utils#505.
* Issue caused by an imcompatibility between sqlalchemy-utils and latest SQLAlchemy 1.4 (see more here kvesteri/sqlalchemy-utils#505).
* pytest-reana 0.7.1 depends on the latest REANA-DB 0.7.3 which fixes an installation problem caused by kvesteri/sqlalchemy-utils#505.
it worked for me when i installed using conda instead of pip. Hope it works for you aswell. |
you can temporarily fix this by changing the imports in
to
|
It seems that #506 is being in the works to fix this |
Pins SQLAlchemy to solve incompatibility of later versions with sqlalchemy-utils. See kvesteri/sqlalchemy-utils#505 Pins Flask-SQLAlchemy due to related apply_driver_hacks issues.
Pins SQLAlchemy to solve incompatibility of later versions with sqlalchemy-utils. See kvesteri/sqlalchemy-utils#505 Pins Flask-SQLAlchemy due to related apply_driver_hacks issues.
The text was updated successfully, but these errors were encountered: