c921954649
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 |
||
|---|---|---|
| .. | ||
| tasks | ||
| templates | ||
| README.rst | ||
README.rst
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