os-win/test-requirements.txt
Lucian Petrut 954693f5ff Use a separate doc requirements file
As per the OpenStack TC decision [1], the doc requirements should
be listed separately.

This also simplifies the requirements handling. At them moment,
we're facing some issues due to conflicting doc related lower
constraints.

While at it, we're bumping the lower constraints based on Nova's
requirements, dropping indirect dependencies which are very difficult
to maintain.

[1] https://governance.openstack.org/tc/reference/project-testing-interface.html

Change-Id: Ifffbb94c069d58df1dbaa1c5a1681312e8455ae2
2020-12-09 13:56:18 +02:00

13 lines
412 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>=3.0.1,<3.1.0 # Apache-2.0
coverage!=4.4,>=4.0 # Apache-2.0
ddt>=1.2.1 # MIT
oslotest>=3.8.0 # Apache-2.0
stestr>=2.0.0 # Apache-2.0
testscenarios>=0.4 # Apache-2.0/BSD
testtools>=2.2.0 # MIT