# 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

coverage>=3.6
ddt>=0.7.0
python-subunit>=0.0.18
sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2
oslosphinx>=2.5.0 # Apache-2.0
oslotest>=1.7.0 # Apache-2.0
testrepository>=0.0.18
testscenarios>=0.4
testtools>=1.4.0
docker-py>=1.4.0 # Apache-2.0
reno>=0.1.1 # Apache2

# 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

coverage>=3.6
ddt>=0.7.0
python-subunit>=0.0.18
sphinx!=1.2.0,!=1.3b1,<1.3,>=1.1.2
oslosphinx>=2.5.0 # Apache-2.0
oslotest>=1.7.0 # Apache-2.0
testrepository>=0.0.18
testscenarios>=0.4
testtools>=1.4.0
docker-py>=1.5.0 # Apache-2.0
reno>=0.1.1 # Apache2

Fix docker-py lib version from 1.4.0+ to 1.5.0+
Fix docker-py lib version from 1.4.0+ to 1.5.0+

The libnetwork related api is introduced since 1.5.0.

Change-Id: I9383b59be0c8c9208d85f6101961e54b421c4ee8
Closes-Bug: #1531879
