We facing errors related to the new pip resolver, this
topic was discussed on the ML and QA team proposed to
to test lower-constraints [1].
I propose to drop this test because the complexity and recurring pain needed
to maintain that now exceeds the benefits provided by this mechanismes.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019390.html
This change includes a backport of I2baa6d318cdbbf86da86cc94171cc7714dbdba3a
which removes the lower-constraints.txt file and its references, and
which completes this change, as suggested by hberaud.
This change also includes a few PEP8 fixes which are branch-specific
and which have been workarounded from victoria onwards.
The fixes don't bump hacking&co (i.e. just a minimal set of changes).
Conflicts:
.zuul.yaml
lower-constraints.txt
They come from the change in the version-specific job template for unit tests,
and a few version-specific changes in lower-contraints.txt.
Change-Id: Ied61e65006ad54803453776e763594e216be1353
(cherry picked from commit e8062fc9e3)
(cherry picked from commit 8b3deb7b5a)
3b51947c36