# 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.
# Metrics and style
hacking!=0.13.0,<0.14,>=0.12.0 # Apache-2.0

# Packaging
mock>=2.0.0 # BSD

# Backends
redis>=2.10.0 # MIT
pymongo!=3.1,>=3.0.2 # Apache-2.0
python-swiftclient>=3.2.0 # Apache-2.0
websocket-client<=0.40.0,>=0.33.0 # LGPLv2+
PyMySQL>=0.7.6 # MIT License

# Unit testing
coverage!=4.4,>=4.0 # Apache-2.0
ddt>=1.0.1 # MIT
doc8>=0.6.0 # Apache-2.0
fixtures>=3.0.0 # Apache-2.0/BSD

testscenarios>=0.4 # Apache-2.0/BSD
testrepository>=0.0.18 # Apache-2.0/BSD
testtools>=2.2.0 # MIT
oslo.db>=4.27.0 # Apache-2.0
testresources>=2.0.0 # Apache-2.0/BSD
os-testr>=1.0.0 # Apache-2.0

# Documentation
sphinx!=1.6.6,>=1.6.2 # BSD
openstackdocstheme>=1.17.0 # Apache-2.0
oslotest>=3.2.0 # Apache-2.0
reno>=2.5.0 # Apache-2.0
os-api-ref>=1.4.0 # Apache-2.0

#OSprofiler
osprofiler>=1.4.0 # Apache-2.0