x/sqlalchemy-migrate
Code Issues Proposed changes

uncap pbr and sqla requirements

Browse Source 
The cap of pbr causes issues now that pbr 1.2 is basically needed for
a lot of projects to do the right thing with requirements ranges. The
sqla capping is preventing new versions of sqla to be used in the
OpenStack gates, and shouldn't be capped by a library.

Change-Id: I5fc142eb8c9d616db2ed9b2f3e4e4d1147e131ff
This commit is contained in:
Sean Dague 2015-07-02 14:03:19 -07:00 committed by Matt Riedemann
parent a94dae7a01
commit 35832555c5
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
requirements.txt
View File

@ -1,9 +1,12 @@
pbr>=0.6,!=0.7,<1.0 # The order of packages is significant, because pip processes them in the order
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.
pbr>=0.11,<2.0
# never put a cap on this, *ever*, sqla versions are handled via # never put a cap on this, *ever*, sqla versions are handled via
# tox, and if SQLA is capped it will only make it so we aren't testing # tox, and if SQLA is capped it will only make it so we aren't testing
# against all the versions we are compatible with. # against all the versions we are compatible with.
SQLAlchemy>=0.7.8,!=0.9.5,<=1.0.99 SQLAlchemy>=0.7.8,!=0.9.5
decorator decorator
six>=1.7.0 six>=1.7.0
sqlparse sqlparse