tahoe-lafs/tahoe-lafs
tahoe-lafs/tahoe-lafs
2
0
Fork 0
Code Issues Pull Requests 23 Packages Projects Releases 1 Wiki Activity

You don't need tox *inside* your test environment.

Browse Source 
You need tox to *manage* your test environment (this is the premise, at least).
This commit is contained in:
Jean-Paul Calderone 2023-04-28 13:32:42 -04:00
parent f48eb81d9d
commit f0b98aead5
2 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.circleci/setup-virtualenv.sh
View File

@ -28,6 +28,10 @@ shift || :
export PIP_FIND_LINKS="file://${WHEELHOUSE_PATH}" export PIP_FIND_LINKS="file://${WHEELHOUSE_PATH}"
export PIP_NO_INDEX="1" export PIP_NO_INDEX="1"
# Get tox inside the bootstrap virtualenv since we use tox to manage the rest
# of the environment.
"${BOOTSTRAP_VENV}"/bin/pip install "tox~=3.0"
# Get everything else installed in it, too. # Get everything else installed in it, too.
"${BOOTSTRAP_VENV}"/bin/tox \ "${BOOTSTRAP_VENV}"/bin/tox \
-c "${PROJECT_ROOT}"/tox.ini \ -c "${PROJECT_ROOT}"/tox.ini \

1
setup.py
View File

@ -416,7 +416,6 @@ setup(name="tahoe-lafs", # also set in __init__.py
"pip==22.0.3", "pip==22.0.3",
"wheel==0.37.1", "wheel==0.37.1",
"setuptools==60.9.1", "setuptools==60.9.1",
"tox~=3.0",
"subunitreporter==22.2.0", "subunitreporter==22.2.0",
"python-subunit==1.4.2", "python-subunit==1.4.2",
"junitxml==0.7", "junitxml==0.7",