397b6fcdf9
The explicit mock package is not required if you can use unittest.mock from python >= 3.3 Change-Id: I1e3a764b38be66b994d790768bc5eb9be4237444
24 lines
898 B
Plaintext
24 lines
898 B
Plaintext
# 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.
|
|
|
|
wheel>=0.32.0 # MIT
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
hacking>=1.1.0,<4.0.0;python_version>='3.6' # Apache-2.0
|
|
mock>=2.0.0,<4.0.0;python_version=='2.7' # BSD
|
|
six>=1.12.0 # MIT
|
|
stestr>=2.1.0,<3.0;python_version=='2.7' # Apache-2.0
|
|
stestr>=2.1.0;python_version>='3.0' # Apache-2.0
|
|
testresources>=2.0.0 # Apache-2.0/BSD
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
testtools>=2.2.0 # MIT
|
|
virtualenv>=20.0.3 # MIT
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
|
|
# optionally exposed by distutils commands
|
|
sphinx!=1.6.6,!=1.6.7,>=1.6.2,<2.0.0;python_version=='2.7' # BSD
|
|
sphinx!=1.6.6,!=1.6.7,>=1.6.2;python_version>='3.4' # BSD
|
|
testrepository>=0.0.18 # Apache-2.0/BSD
|
|
|
|
pre-commit>=2.6.0;python_version>='3.6' # MIT
|