Python: Package selection criteria

[jpmckinney]

At https://ocp-software-handbook.readthedocs.io/en/latest/python/preferred_packages.html, we can add criteria for selecting packages, like:

• The package is properly released (PyPI readme, changelog, git tags, etc.).
• The package's repository does not indicate that it is archived or unmaintained.
• Supports the most recent version of Python and frameworks (e.g. Django, Sphinx)
  • This frequently implies that the library has been updated within the last year (easy to tell on PyPI)
  • Simpler libraries might not need changes for new Python versions.
  • This came up recently with django-tastypie (which has now been updated).
• Meets the QASP criteria.
  • Ideally, the repository has a badge for test coverage and build status so that this is easy to determine.
• The package's issue tracker shows that issues are responded to in a timely manner.
  • The maintainer's other repositories can also be taken into consideration if the repository is fairly new or unpopular.
  • This came up recently with django-environ (https://github.com/OpenDataServices/lib-cove-web/issues/80, https://github.com/joke2k/django-environ/pull/291).