system-config/playbooks/roles/create-venv
Tony Breeds 500fc92f17 Fix task name to reflect correct distro
Change-Id: I4ac5bdd6ab27c460b8864b75157a8487128d5a76
2024-07-09 09:12:13 +10:00
..
tasks Fix task name to reflect correct distro 2024-07-09 09:12:13 +10:00
templates create-venv: make upgrade venv once per day 2022-12-06 17:28:09 +11:00
README.rst create-venv: add role; use in install-borg 2022-08-10 10:14:51 +10:00

Create a venv

You would think this role is unnecessary and roles could just install a venv directly ... except sometimes pip/setuptools get out of date on a platform and can't understand how to install compatible things. For example the pip shipped on Bionic will upgrade itself to a version that doesn't support Python 3.6 because it doesn't understand the metadata tags the new version marks itself with. We've seen similar problems with wheels. History has shown that whenever this problem appears solved, another issue will appear. So for reasons like this, we have this as a synchronization point for setting up venvs.

Role Variables