system-config/playbooks/roles/create-venv
Ian Wienand c921954649
pip: use latest instead of upgrade
I'm not sure if this is clearer or not (which is why I proposed it
separately here).

From inspection of the code, adding "state: latest" just means Ansible
runs "install -U" ... which is pretty much the same thing as adding
--upgrade.  Which is clearer, I'm not sure?

Change-Id: I6e31523686555e33d062f3b05f2385d7e21e2620
2022-12-06 17:28:09 +11:00
..
tasks pip: use latest instead of upgrade 2022-12-06 17:28:09 +11: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