Port variant py38
Summary Package to manage versions by scm tags (PY38)
Package version 6.3.2
Keywords python
Maintainer Python Automaton
License Not yet specified
Other variants py39
Ravenports Buildsheet | History
Ravensource Port Directory | History
Last modified 14 SEP 2021, 23:34:25 UTC
Port created 20 APR 2020, 15:00:59 UTC
Subpackage Descriptions
single setuptools_scm ============== setuptools_scm handles managing your Python package versions in SCM 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 ````. 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 `` 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", "wheel", "setuptools_scm>=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 ```` 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 `` 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``. 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/" ```` 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 ```` 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( ..., use_scm_version=True, setup_requires=['setuptools_scm'], ..., ) Arguments to ``get_version()`` (see below) may be passed as a dictionary to use_scm_version. For example: .. code:: python from setuptools import setup
Configuration Switches (platform-specific settings discarded)
PY38 ON Build using Python 3.8 PY39 OFF Build using Python 3.9
Package Dependencies by Type
Build (only) python-pip:single:py38
Build and Runtime python38:single:standard
Runtime (only) python-packaging:single:py38
Download groups
main mirror://PYPIWHL/bc/bf/353180314d0e27929703faf240c244f25ae765e01f595a010cafb209ab51
Distribution File Information
4c64444b1d49c4063ae60bfe1680f611c8b13833d556fd1d6050c0023162a119 33239 setuptools_scm-6.3.2-py3-none-any.whl
Ports that require python-setuptools-scm:py38
python-borgbackup:py38 Deduplicated, encrypted, compressed backups (PY38)
python-cffsubr:py38 CFF subroutinizer based on AFDKO tx tool (PY38)
python-lazy-object-proxy:py38 Fast and thorough lazy object proxy (PY38)
python-psautohint:py38 Wrapper for Adobe's PostScript autohinter (PY38)
python-pyclipper:py38 Cython wrapper for the AJ Clipper library (PY38)
python-pyocr:py38 Wrapper for OCR engines (Tesseract, etc) (PY38)
python-skia-pathops:py38 Skia library bindings (PY38)