@@ -2564,7 +2564,7 @@ easily do so by updating the ``common_packages`` setting.
In addition to system packages, the ``common`` role makes it easy to check if
any of the pip requirements files are outdated as well. It should be noted,
though, that this check does *not* verify the Python virtual environments
themselves.
themselves. Only Python 3 is supported at this time.
This is primarily useful when you use `pip-tools
<https://github.com/jazzband/pip-tools>`_ for maintaining the
@@ -2575,9 +2575,7 @@ environment in sync and up-to-date.
Roles that want to take advantage of this would:
- Create a sub-directory under
``/etc/pip_check_requirements_upgrades/`` (for Python 2
applications) or ``/etc/pip_check_requirements_upgrades-py3/`` (for
Python 3 applications).
``/etc/pip_check_requirements_upgrades/``.
- Deploy ``.in`` and ``.txt`` files within the sub-directory (see ``pip-tools``
docs for explanation of how the ``.in`` files work).
- Ensure the created sub-directory and files have ownership set to