From 35832555c5ede7148bedbfec0d79351d90a93b53 Mon Sep 17 00:00:00 2001 From: Sean Dague Date: Thu, 2 Jul 2015 14:03:19 -0700 Subject: [PATCH] uncap pbr and sqla requirements 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 --- requirements.txt | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/requirements.txt b/requirements.txt index 4d60d8b..d475532 100644 --- a/requirements.txt +++ b/requirements.txt @@ -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 # tox, and if SQLA is capped it will only make it so we aren't testing # 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 six>=1.7.0 sqlparse