While setting-up the Python virtual environment, the wsgi_website role will try to install specific versions of pip and setuptools, which will cause playbook runs not to be idempotent in situations where roles depending on it are trying to install specific versions of those two packages explicitly.

Instead of doing something like this, it would be better if the role would not explicitly install pip/setuptools, since those two packages seem to be kept up-to-date automatically during the creation of virtual environment itself.

The following should be done:

1. Update the wsgi_website role.

   1. Do not enforce specific versions of setuptools/pip when creating the new virtual environment.

2. Update the role reference documentation (if relevant).

3. Update the usage instructions (if relevant).

4. Update release notes.