# 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.

hacking<0.11,>=0.10.0

Mako>=0.4.0
PrettyTable<0.8,>=0.7
PyMySQL>=0.6.2 # MIT License
bashate>=0.2 # Apache-2.0
coverage>=3.6
fixtures>=1.3.1
mock>=1.2
oslosphinx>=2.5.0 # Apache-2.0
oslotest>=1.10.0 # Apache-2.0
psycopg2>=2.5
pylint==1.4.4 # GNU GPL v2
rfc3986>=0.2.0 # Apache-2.0
sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2
sphinxcontrib-httpdomain
tempest-lib>=0.9.0
testrepository>=0.0.18
testscenarios>=0.4
testtools>=1.4.0

python-saharaclient>=0.10.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.

hacking<0.11,>=0.10.0

Mako>=0.4.0
PrettyTable<0.8,>=0.7
PyMySQL>=0.6.2 # MIT License
bashate>=0.2 # Apache-2.0
coverage>=3.6
fixtures>=1.3.1
mock>=1.2
oslosphinx>=2.5.0 # Apache-2.0
oslotest>=1.10.0 # Apache-2.0
psycopg2>=2.5
pylint==1.4.4 # GNU GPL v2
rfc3986>=0.2.0 # Apache-2.0
sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2
sphinxcontrib-httpdomain
tempest-lib>=0.9.0
testrepository>=0.0.18
testresources>=0.2.4
testscenarios>=0.4
testtools>=1.4.0

python-saharaclient>=0.10.0

Add testresources used by oslo.db fixture
Add testresources used by oslo.db fixture

If we use oslo.db fixtures, we'll need the package or
the next version of oslo.db release will break us.

manually picked from: I176c85551007d3d9e7de8896ad12e9b87ff278d8
for more information see: I1e06e77308a7dd23209124f0807d61fb52470188

Change-Id: Ib511ec705206b2168fe18f5870ca81d59b7ba89f
Closes-Bug: 1503501
