vagrant: use the latest python 3.11.7 for binary builds

This commit is contained in:
Thomas Waldmann 2024-01-10 22:10:54 +01:00
parent 73a416830a
commit a6f224f031
No known key found for this signature in database
GPG Key ID: 243ACFA951F78E01
1 changed files with 5 additions and 5 deletions

10
Vagrantfile vendored
View File

@ -244,7 +244,7 @@ def install_pythons(boxname)
. ~/.bash_profile
echo "PYTHON_CONFIGURE_OPTS: ${PYTHON_CONFIGURE_OPTS}"
pyenv install 3.12.0 # tests
pyenv install 3.11.5 # tests, binary build
pyenv install 3.11.7 # tests, binary build
pyenv install 3.10.2 # tests
pyenv install 3.9.10 # tests
pyenv rehash
@ -264,8 +264,8 @@ def build_pyenv_venv(boxname)
. ~/.bash_profile
cd /vagrant/borg
# use the latest 3.11 release
pyenv global 3.11.5
pyenv virtualenv 3.11.5 borg-env
pyenv global 3.11.7
pyenv virtualenv 3.11.7 borg-env
ln -s ~/.pyenv/versions/borg-env .
EOF
end
@ -311,8 +311,8 @@ def run_tests(boxname, skip_env)
. ../borg-env/bin/activate
if which pyenv 2> /dev/null; then
# for testing, use the earliest point releases of the supported python versions:
pyenv global 3.9.10 3.10.2 3.11.5 3.12.0
pyenv local 3.9.10 3.10.2 3.11.5 3.12.0
pyenv global 3.9.10 3.10.2 3.11.7 3.12.0
pyenv local 3.9.10 3.10.2 3.11.7 3.12.0
fi
# otherwise: just use the system python
# some OSes can only run specific test envs, e.g. because they miss FUSE support: