24fe404d97
We shouldn't be able to bump global requirement versions if that would be incompatible with the current test set of versions. To assess 'works' we need to run them in tests which means that we need to update upper-constraints.txt at the same time. We don't test all versions however, so just checking that the constraints version is compatible with the updated global requirements is sufficient. This adds a dependency on the pypa packaging library. The library is maintained by the authors of setuptools and pip, is Apache V2, in good condition and Python 3 ready. Its a test-only dependency so I don't think the distro packaging status matters. This is *the* reference library for packaging facilities on Python. Change-Id: I032dd9a384453dcfa4911ea905c8f89b0c974211
12 lines
448 B
Plaintext
12 lines
448 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.
|
|
# NOTE: These are requirements for testing the requirements project only
|
|
# See global-requirements for the actual requirements list
|
|
hacking<0.11,>=0.10
|
|
packaging
|
|
testrepository>=0.0.18
|
|
testscenarios>=0.4
|
|
testtools>=1.4.0
|
|
virtualenv
|