Configure `tox` to use `venv` (#12015)
As the comment says, virtualenv is a pile of fail.
This commit is contained in:
parent
e69f8f0a8e
commit
6127c4b9f1
|
@ -8,7 +8,9 @@ export DEBIAN_FRONTEND=noninteractive
|
|||
set -ex
|
||||
|
||||
apt-get update
|
||||
apt-get install -y python3 python3-dev python3-pip libxml2-dev libxslt-dev xmlsec1 zlib1g-dev tox libjpeg-dev libwebp-dev
|
||||
apt-get install -y \
|
||||
python3 python3-dev python3-pip python3-venv \
|
||||
libxml2-dev libxslt-dev xmlsec1 zlib1g-dev tox libjpeg-dev libwebp-dev
|
||||
|
||||
export LANG="C.UTF-8"
|
||||
|
||||
|
|
|
@ -0,0 +1 @@
|
|||
Configure `tox` to use `venv` rather than `virtualenv`.
|
5
tox.ini
5
tox.ini
|
@ -4,6 +4,11 @@ envlist = packaging, py37, py38, py39, py310, check_codestyle, check_isort
|
|||
# we require tox>=2.3.2 for the fix to https://github.com/tox-dev/tox/issues/208
|
||||
minversion = 2.3.2
|
||||
|
||||
# the tox-venv plugin makes tox use python's built-in `venv` module rather than
|
||||
# the legacy `virtualenv` tool. `virtualenv` embeds its own `pip`, `setuptools`,
|
||||
# etc, and ends up being rather unreliable.
|
||||
requires = tox-venv
|
||||
|
||||
[base]
|
||||
deps =
|
||||
python-subunit
|
||||
|
|
Loading…
Reference in New Issue