4469a813cb
While exploring removing unused packages from lower-constraints.txt it became clear that the lower-constraints job was not working as expected: Because our tox config has usedevelop=True 'setup.py develop' is called to install the placement package after the install command is called. This means that the lower-constraints are clobbered. I had mistakenly assumed that turning off 'usedevelop', which causes 'setup.py install' would not make any difference, because it usually installs dependencies too. It turns out however, that when using pbr and within a git working dir, it does not. That took some time to figure out. Oh well. This change makes it so that we create the tox environment using usedevelop=False and with our own install_command, to avoid upper constraints conflicting with lower constraints. This flagged up a few changes, the main one being that we did not have a new enough version of keystonemiddleware in order to require use of www_authenticate_uri. requirements.txt is updated for this as well. And PasteDeploy needed to be updated to work with Python 3's notion of namespace packages. psycopg2 need a newer version to work with Postgresql 10. oslotest needs to be raised to 3.4.0 because the tests in cmd.test_manage use features to control what is capture by the Output fixture from oslotest. Note that the lower-constraints job found this problem and also demonstrates why we must run the lower-constraints job without upper-constraints being involved. upper-constraints will "win" and we don't want that. The point of the job is find packages where lower-constraints are wrong, so it must "win". The end result here is a lower-constraints.txt file that starts from the lower-constraints.txt defined by nova, and then is adapted to update the versions of packages that were not up to date, remove those packages which are no longer present, and add some that are now required. Change-Id: Id66a28f7ace6fc2adf0e1201d9de5f901234d870
19 lines
594 B
Plaintext
19 lines
594 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!=0.13.0,<0.14,>=0.12.0 # Apache-2.0
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
mock>=2.0.0 # BSD
|
|
psycopg2>=2.6.2 # LGPL/ZPL
|
|
PyMySQL>=0.7.6 # MIT License
|
|
oslotest>=3.4.0 # Apache-2.0
|
|
stestr>=1.0.0 # Apache-2.0
|
|
testtools>=2.2.0 # MIT
|
|
bandit>=1.1.0 # Apache-2.0
|
|
gabbi>=1.35.0 # Apache-2.0
|
|
|
|
# placement functional tests
|
|
wsgi-intercept>=1.7.0 # MIT License
|