hacking>=0.10.2,<0.11  # Apache-2.0

bashate>=0.2 # Apache-2.0
coverage>=3.6
discover
fixtures>=1.3.1
python-subunit>=0.0.18  # Apache-2.0/BSD
python-swiftclient>=2.7.0  # Apache-2.0
sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3  # BSD
oslosphinx>=2.5.0,!=3.4.0  # Apache-2.0
oslotest>=1.10.0  # Apache-2.0
os-testr>=0.4.1 # Apache-2.0
testrepository>=0.0.18  # Apache-2.0/BSD
testscenarios>=0.4  # Apache-2.0/BSD
testtools>=1.4.0  # MIT
mock>=1.2  # BSD

hacking>=0.10.2,<0.11  # Apache-2.0

bashate>=0.2 # Apache-2.0
coverage>=3.6
discover
fixtures>=1.3.1
pycrypto>=2.6  # Public Domain
python-subunit>=0.0.18  # Apache-2.0/BSD
python-swiftclient>=2.7.0  # Apache-2.0
sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3  # BSD
oslosphinx>=2.5.0,!=3.4.0  # Apache-2.0
oslotest>=1.10.0  # Apache-2.0
os-testr>=0.4.1 # Apache-2.0
testrepository>=0.0.18  # Apache-2.0/BSD
testscenarios>=0.4  # Apache-2.0/BSD
testtools>=1.4.0  # MIT
mock>=1.2  # BSD

Add req to pycrypto to fix import errors
Add req to pycrypto to fix import errors

We're not sure...

But we think paramiko's recent 2.0.0 release somehow breaks a
requirement chain where *somebody* needs pycrypto and is no longer
getting it.  Adding the requirement for pycrypto (synced with the
corresponding global requirement) resolves the tox errors seen in the
bug report.

And the gate wasn't failing because... the pycrypto req was being picked
up some other way.

Change-Id: I1286b7df7df6608a2fdb929eb55f2d6fbfd031ea
Closes-Bug: 1576822
