CI: Use [tox]requires to pin virtualenv

Code Issues Proposed changes

Using an antiquated distro to keep us on an EOL'ed version of python
that *just so happens* to have had support dropped for it around the
same time virtualenv removed the ability to create py27 environments
doesn't seem like the right way to address the problem.
Make sure we also include the tox<4 pin that we're using project-wide
so we don't get some nonsense about "Multiple top-level packages
discovered in a flat-layout".
Related-Change: https://review.opendev.org/c/openstack/swift/+/881035
Change-Id: I32a161e555179ca34d306ac37e4097611853e36b

This commit is contained in:

Tim Burke

2023年04月26日 10:54:01 -07:00

parent 0a970d0736

commit 0518c60235

2 changed files with 6 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

5
tox.ini

View File

@@ -1,6 +1,11 @@

[tox]

envlist = py37,py27,pep8

minversion = 3.18.0

requires =

# required to support py27/py36 envs

virtualenv<20.22

# project-wide requirement; see .zuul.yaml

tox<4

[pytest]

addopts = --verbose

CI: Use [tox]requires to pin virtualenv

5 tox.ini Unescape Escape View File

5
tox.ini

View File