275c132fd5
pip 20.3 brings in a strict dependency resolver which is enabled by default. This causes our lower-constraints tests to fail, because the requirement files were out of date from reality - they had conflicting requirements which previous versions of pip were ignoring. Let's catch up package versions to newer ones that are supported in the python runtimes that the Wallaby release will be deployed to. [1] http://pyfound.blogspot.com/2020/11/pip-20-3-new-resolver.html [2] https://pip.pypa.io/en/stable/user_guide/#changes-to-the-pip-dependency-resolver-in-20-3-2020 Change-Id: I6ddd11535e9365e8b55a6829967b886c2253d6f0
16 lines
546 B
Plaintext
16 lines
546 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.1.0,<3.2.0 # Apache-2.0
|
|
coverage>=5.2.1 # Apache-2.0
|
|
ddt>=1.4.1 # MIT
|
|
python-subunit>=1.4.0 # Apache-2.0/BSD
|
|
pytest>=5.3.5 # MIT
|
|
testrepository>=0.0.20 # Apache-2.0/BSD
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
testtools>=2.4.0 # MIT
|
|
# integration tests requirements
|
|
selenium>=2.50.1 # Apache-2.0
|
|
xvfbwrapper>=0.1.3 #license: MIT
|