zhmcclient / python-zhmcclient / test-2635

80%

push

github

Migrated to pyproject.toml

Details:

* Dev: Migrated from setup.py to pyproject.toml with setuptools as build
  backend. This provides for automatic determination of the package version
  without having to edit a version file.

* In addition to the `zhmcclient.__version__` property which provides the
  package version as a string, a new `zhmcclient.__version_tuple__` property
  provides it as a tuple of integer values.

More internal details (not in change log):

* setuptools-scm generates the versions into a new file
  zhmcclient/_version_scm.py, which gets imported into zhmcclient/_version.py
  to maintain its interface. The new _version_scm.py file is ignored by git.
  and excluded from package_py_files, so it is no longer included in flake8
  or pylint checks (where it would fail).

* Removed inclusion of other requirements/constraints files with '-r' and '-c'
  because the dynamic support for dependencies in setuptools does not
  support these options. This has been replaced by ensuring that the
  "included" files are honored, in the Makefile.

* Renamed minimum-constraints.txt to minimum-constraints-develop.txt
  because it no longer includes minimum-constraints-install.txt

* Renamed .safety-policy-all.yml to .safety-policy-develop.yml to match
  its scope of only covering development dependencies.

* Added a base-requirements.txt file for basic dependents needed for
  pip and automatic package version detection. This replaces the rather
  hard coded installation of pip,setuptools,wheel in the Makefile.
  It also removes the support for first ensuring the minimum version
  of pip to be >=9.0.1 before using requirements files.

* Adjusted the retrieval of the package version in docs/conf.py to the new
  version file created by setuptools-scm. This caused any Sphinx commands
  now to depend on the wheel archive, since that is the step that creates
  the setuptools-scm version file.

* Updated the release description in docs/development.rst to no... (continued)

4 of 4 new or added lines in 1 file covered. (100.0%)

7960 of 9926 relevant lines covered (80.19%)

6.41 hits per line