libvirt-python/setup.cfg

[metadata]
name = libvirt-python
version = file: VERSION
description = The libvirt virtualization API python binding
long_description = file: README
long_description_content_type = text/x-rst
url = http://www.libvirt.org
maintainer = Libvirt Maintainers
maintainer_email = libvir-list@redhat.com
license_files = COPYING
classifiers =
      Development Status :: 5 - Production/Stable
      Intended Audience :: Developers
      License :: OSI Approved :: GNU Lesser General Public License v2 or later (LGPLv2+)
      Programming Language :: Python :: 3 :: Only

[options]
python_requires = >=3.6
package_dir =
    =build
Move declarative stuff out of setup.py to setup.cfg So, why using setup.cfg if pyproject.toml is the new best thing recommended everywhere? Well, quite a few of the fields we use with setuptools are setuptools-specific and haven't been introduced as keywords to pyproject.toml yet. There is a chance that these fields could be added via a dedicated 'tool.setuptools' TOML section, but none of it is officially documented and so it would be BETA at best anyway. Let's not try our luck and use a declarative config file tailored specifically to setuptools - setup.cfg. It's also unlikely we'd switch from setuptools to something else in the near future given the nature of building this project (i.e. building with C modules) and if so, it would likely not be a PyPa recommended PEP-517 compliant build system anyway, e.g. meson, so we're totally fine doing this. Signed-off-by: Erik Skultety <eskultet@redhat.com> 2023-06-06 15:01:57 +03:00			`[metadata]`
			`name = libvirt-python`
setup: Query library version out of a file This makes it possible to programatically query the version in any stage of the build process, including Makefile etc. Signed-off-by: Erik Skultety <eskultet@redhat.com> 2023-06-08 11:57:15 +03:00			`version = file: VERSION`
Move declarative stuff out of setup.py to setup.cfg So, why using setup.cfg if pyproject.toml is the new best thing recommended everywhere? Well, quite a few of the fields we use with setuptools are setuptools-specific and haven't been introduced as keywords to pyproject.toml yet. There is a chance that these fields could be added via a dedicated 'tool.setuptools' TOML section, but none of it is officially documented and so it would be BETA at best anyway. Let's not try our luck and use a declarative config file tailored specifically to setuptools - setup.cfg. It's also unlikely we'd switch from setuptools to something else in the near future given the nature of building this project (i.e. building with C modules) and if so, it would likely not be a PyPa recommended PEP-517 compliant build system anyway, e.g. meson, so we're totally fine doing this. Signed-off-by: Erik Skultety <eskultet@redhat.com> 2023-06-06 15:01:57 +03:00			`description = The libvirt virtualization API python binding`
			`long_description = file: README`
			`long_description_content_type = text/x-rst`
			`url = http://www.libvirt.org`
			`maintainer = Libvirt Maintainers`
			`maintainer_email = libvir-list@redhat.com`
			`license_files = COPYING`
			`classifiers =`
			`Development Status :: 5 - Production/Stable`
			`Intended Audience :: Developers`
			`License :: OSI Approved :: GNU Lesser General Public License v2 or later (LGPLv2+)`
			`Programming Language :: Python :: 3 :: Only`

			`[options]`
			`python_requires = >=3.6`
			`package_dir =`
			`=build`