Bug 1834350 [wpt PR 40130] - Don't require virtualenv binary, a=testonly
commitbecb9e4fae1ad99abeb7077ceb4ac94fd1ccc1c4
authorJames Graham <james@hoppipolla.co.uk>
Sat, 10 Jun 2023 10:29:30 +0000 (10 10:29 +0000)
committermoz-wptsync-bot <wptsync@mozilla.com>
Tue, 13 Jun 2023 07:14:18 +0000 (13 07:14 +0000)
tree92f63068662ed76dd5accac0bbf07db255446d9e
parent575a0b7a30e0ed987c9fddd8a0839c630f016b45
Bug 1834350 [wpt PR 40130] - Don't require virtualenv binary, a=testonly

Automatic update from web-platform-tests
Don't require virtualenv binary

With Python 3 we can use python3 -m venv to create a virtualenv.

The main dififculty is that we're missing activate_this.py which we use
to activate the environment. But we can do the relevant path / env manipulations
ourselves and so cut down the number of dependencies.

--
Try falling back to `pip` if `pip3` doesn't exist

--
Update documentation

--

wpt-commits: 7eed90bb584ed77bf7227233501882a43f90d05e5bb7544e8c50cb3bcc55bd4508cbbc94b12093024fd791ba8cda63f0fdece4bdb72a431f198b582e
wpt-pr: 40130
testing/web-platform/tests/.taskcluster.yml
testing/web-platform/tests/docs/running-tests/from-local-system.md
testing/web-platform/tests/tools/ci/tc/tasks/test.yml
testing/web-platform/tests/tools/docker/Dockerfile
testing/web-platform/tests/tools/wpt/virtualenv.py