64a90a6700
Project Testing Interface for Python [0] suggests to use stestr as unit test runner uniformly across all OpenStack projects. [0] https://governance.openstack.org/tc/reference/pti/python.html Change-Id: I1c321500a2256b09cb6a58f6cd7070c9dc702555
22 lines
712 B
Plaintext
22 lines
712 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.
|
|
hacking>=1.0.0,<1.1.0 # Apache-2.0
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
doc8>=0.6.0 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
mock>=2.0.0 # BSD
|
|
Babel!=2.4.0,>=2.3.4 # BSD
|
|
PyMySQL>=0.7.6 # MIT License
|
|
iso8601>=0.1.11 # MIT
|
|
oslotest>=3.2.0 # Apache-2.0
|
|
stestr # Apache-2.0
|
|
psycopg2>=2.6.2 # LGPL/ZPL
|
|
testtools>=2.2.0 # MIT
|
|
testresources>=2.0.0 # Apache-2.0/BSD
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
WebTest>=2.0.27 # MIT
|
|
bashate>=0.5.1 # Apache-2.0
|
|
flake8-import-order>=0.13 # LGPLv3
|
|
Pygments>=2.2.0 # BSD
|