Bump SQLAlchemy upper bound.
SQLAlchemy 1.0.x should just work. So move the cap to 1.1 as suggested by Mike Bayer, the SQLAlchemy maintainer. "I would note that capping under 1.1 might be a good idea. Each 1.x, 1.y, etc. is where we might make bigger changes." - Michael Bayer Change-Id: I0f9ac55122f04c9acd11e382219dfd562035faea
This commit is contained in:
parent
fceaa48541
commit
e59efee4fe
@ -161,7 +161,7 @@ fasteners>=0.5 # Apache-2.0
|
||||
simplejson>=2.2.0
|
||||
six>=1.9.0
|
||||
sockjs-tornado>=1.0.0,<2.0.0
|
||||
SQLAlchemy>=0.9.7,<=0.9.99
|
||||
SQLAlchemy>=0.9.7,<1.1.0
|
||||
sqlalchemy-migrate>=0.9.6
|
||||
sqlalchemy-utils # BSD License
|
||||
stevedore>=1.3.0 # Apache-2.0
|
||||
|
Loading…
x
Reference in New Issue
Block a user