# Buildsheet autogenerated by ravenadm tool -- Do not edit. NAMEBASE= python-setuptools-scm VERSION= 7.0.5 KEYWORDS= python VARIANTS= py39 py310 SDESC[py310]= Package to manage versions by scm tags (3.10) SDESC[py39]= Package to manage versions by scm tags (3.9) HOMEPAGE= https://github.com/pypa/setuptools_scm/ CONTACT= Python_Automaton[python@ironwolf.systems] DOWNLOAD_GROUPS= main SITES[main]= PYPIWHL/01/ed/75a20e7b075e8ecb1f84e8debf833917905d8790b78008915bd68dddd5c4 DISTFILE[1]= setuptools_scm-7.0.5-py3-none-any.whl:main DF_INDEX= 1 SPKGS[py310]= single SPKGS[py39]= single OPTIONS_AVAILABLE= PY39 PY310 OPTIONS_STANDARD= none VOPTS[py310]= PY39=OFF PY310=ON VOPTS[py39]= PY39=ON PY310=OFF DISTNAME= setuptools_scm-7.0.5.dist-info GENERATED= yes [PY39].RUN_DEPENDS_ON= python-packaging:single:py39 python-setuptools:single:py39 python-tomli:single:py39 python-typing-extensions:single:py39 [PY39].USES_ON= python:py39,wheel [PY310].RUN_DEPENDS_ON= python-packaging:single:py310 python-setuptools:single:py310 python-tomli:single:py310 python-typing-extensions:single:py310 [PY310].USES_ON= python:py310,wheel [FILE:2922:descriptions/desc.single] setuptools_scm ============== setuptools_scm extract Python package versions from git or hg metadata instead of declaring them as the version argument or in a SCM managed file. Additionally setuptools_scm provides setuptools with a list of files that are managed by the SCM (i.e. it automatically adds all of the SCM-managed files to the sdist). Unwanted files must be excluded by discarding them via ``MANIFEST.in``. setuptools_scm support the following scm out of the box: * git * mercurial ``pyproject.toml`` usage ------------------------ The preferred way to configure setuptools_scm is to author settings in a ``tool.setuptools_scm section of pyproject.toml``. This feature requires Setuptools 42 or later, released in Nov, 2019. If your project needs to support build from sdist on older versions of Setuptools, you will need to also implement the ``setup.py usage`` for those legacy environments. First, ensure that setuptools_scm is present during the project's built step by specifying it as one of the build requirements. .. code:: toml # pyproject.toml [build-system] requires = ["setuptools>=45", "setuptools_scm[toml]>=6.2"] That will be sufficient to require setuptools_scm for projects that support PEP 518 ([pip] and [pep517]). Many tools, especially those that invoke ``setup.py`` for any reason, may continue to rely on setup_requires. For maximum compatibility with those uses, consider also including a setup_requires directive (described below in ``setup.py usage and setup.cfg``). To enable version inference, add this section to your ``pyproject.toml``: .. code:: toml # pyproject.toml [tool.setuptools_scm] Including this section is comparable to supplying ``use_scm_version=True in setup.py``. Additionally, include arbitrary keyword arguments in that section to be supplied to ``get_version()``. For example: .. code:: toml # pyproject.toml [tool.setuptools_scm] write_to = "pkg/_version.py" If you need to confirm which version string is being generated or debug the configuration, you can install `setuptools-scm `_ directly in your working environment and run: .. code-block:: shell $ python -m setuptools_scm # To explore other options, try: $ python -m setuptools_scm --help ``setup.py`` usage (deprecated) ------------------------------- .. warning:: setup_requires has been deprecated in favor of ``pyproject.toml The following settings are considered legacy behavior and superseded by the pyproject.toml`` usage, but for maximal compatibility, projects may also supply the configuration in this older form. To use setuptools_scm just modify your project's ``setup.py`` file like this: * Add setuptools_scm to the setup_requires parameter. * Add the use_scm_version parameter and set it to True. For example: .. code:: python from setuptools import setup setup( [FILE:116:distinfo] 7930f720905e03ccd1e1d821db521bff7ec2ac9cf0ceb6552dd73d24a45d3b02 42908 setuptools_scm-7.0.5-py3-none-any.whl