1 # Buildsheet autogenerated by ravenadm tool -- Do not edit.
3 NAMEBASE= python-setuptools-scm
7 SDESC[py310]= Package to manage versions by scm tags (3.10)
8 SDESC[v11]= Package to manage versions by scm tags (3.11)
9 HOMEPAGE= https://github.com/pypa/setuptools_scm/
10 CONTACT= Python_Automaton[python@ironwolf.systems]
13 SITES[main]= PYPIWHL/1d/66/8f42c941be949ef2b22fe905d850c794e7c170a526023612aad5f3a121ad
14 DISTFILE[1]= setuptools_scm-7.1.0-py3-none-any.whl:main
19 OPTIONS_AVAILABLE= PY310 PY311
20 OPTIONS_STANDARD= none
21 VOPTS[py310]= PY310=ON PY311=OFF
22 VOPTS[v11]= PY310=OFF PY311=ON
24 DISTNAME= setuptools_scm-7.1.0.dist-info
28 [PY310].RUN_DEPENDS_ON= python-packaging:single:py310
29 python-setuptools:single:py310
30 python-typing-extensions:single:py310
31 python-tomli:single:py310
32 [PY310].USES_ON= python:py310,wheel
34 [PY311].RUN_DEPENDS_ON= python-packaging:single:v11
35 python-setuptools:single:v11
36 python-typing-extensions:single:v11
37 [PY311].USES_ON= python:v11,wheel
39 [FILE:3000:descriptions/desc.single]
43 setuptools_scm extracts Python package versions from git or
44 hg metadata instead of declaring them as the version argument
45 or in a SCM managed file.
47 Additionally setuptools_scm provides setuptools with a list of
48 files that are managed by the SCM (i.e. it automatically adds all of
49 the SCM-managed files to the sdist). Unwanted files must be excluded
50 by discarding them via ``MANIFEST.in``.
52 setuptools_scm supports the following scm out of the box:
57 ``pyproject.toml`` usage
58 ------------------------
60 The preferred way to configure setuptools_scm is to author
61 settings in a ``tool.setuptools_scm section of pyproject.toml``.
63 This feature requires Setuptools 42 or later, released in Nov, 2019.
64 If your project needs to support build from sdist on older versions
65 of Setuptools, you will need to also implement the ``setup.py usage``
66 for those legacy environments.
68 First, ensure that setuptools_scm is present during the project's
69 built step by specifying it as one of the build requirements.
75 requires = ["setuptools>=45", "setuptools_scm[toml]>=6.2"]
77 That will be sufficient to require setuptools_scm for projects
78 that support PEP 518 ([pip] and
79 [pep517]). Many tools,
80 especially those that invoke ``setup.py`` for any reason, may
81 continue to rely on setup_requires. For maximum compatibility
82 with those uses, consider also including a setup_requires directive
83 (described below in ``setup.py usage and setup.cfg``).
85 To enable version inference, you need to set the version
86 dynamically in the project section of ``pyproject.toml``:
92 # version = "0.0.1" # Remove any existing version parameter.
95 Then add this section to your ``pyproject.toml``:
100 [tool.setuptools_scm]
102 Including this section is comparable to supplying
103 ``use_scm_version=True in setup.py``. Additionally,
104 include arbitrary keyword arguments in that section
105 to be supplied to ``get_version()``. For example:
110 [tool.setuptools_scm]
111 write_to = "pkg/_version.py"
113 Where pkg is the name of your package.
115 If you need to confirm which version string is being generated
116 or debug the configuration, you can install
117 `setuptools-scm <https://github.com/pypa/setuptools_scm>`_
118 directly in your working environment and run:
120 .. code-block:: shell
122 $ python -m setuptools_scm
124 # To explore other options, try:
125 $ python -m setuptools_scm --help
127 ``setup.py`` usage (deprecated)
128 -------------------------------
132 setup_requires has been deprecated in favor of ``pyproject.toml
134 The following settings are considered legacy behavior and
135 superseded by the pyproject.toml`` usage, but for maximal
136 compatibility, projects may also supply the configuration in
139 To use setuptools_scm just modify your project's ``setup.py`` file
143 73988b6d848709e2af142aa48c986ea29592bbcfca5375678064708205253d8e 43829 setuptools_scm-7.1.0-py3-none-any.whl