robojerk/codeql-action

python-setup: rely on new virtualenv for venv creation in Ubuntu 22.04

Browse source 
Removes the hotfix from https://github.com/github/codeql-action/pull/1257
This commit is contained in:
Rasmus Wriedt Larsen 2022-11-29 11:43:01 +01:00
parent 9dac9f748a
commit c62445de22
No known key found for this signature in database
2 changed files with 11 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

4
python-setup/install_tools.ps1
View file

@ -4,8 +4,8 @@
# version of `setuptools` to ensure that binaries are always put under
# `<venv-path>/bin`, which wouldn't always happen with the GitHub actions version of
# Ubuntu 22.04. See https://github.com/github/codeql-action/issues/1249
py -2 -m pip install --user --upgrade pip 'setuptools<60' wheel
py -3 -m pip install --user --upgrade pip 'setuptools<60' wheel
py -2 -m pip install --user --upgrade pip setuptools wheel
py -3 -m pip install --user --upgrade pip setuptools wheel
# virtualenv is a bit nicer for setting up virtual environment, since it will provide up-to-date versions of
# pip/setuptools/wheel which basic `python3 -m venv venv` won't