setuptools-us4us
Common setuptools extensions used by the us4us Python packages, e.g. determining the package version from the state of the git repository (release tags and branches).
Installation
pip install setuptools_us4us
Usually it is needed only at build time, e.g. in the project's pyproject.toml:
[build-system]
requires = ["setuptools>=61", "wheel", "setuptools_us4us"]
build-backend = "setuptools.build_meta"
and setup.py:
import setuptools
from setuptools_us4us import setup_version
setuptools.setup(
name="my_package",
# also writes my_package/version.py (__version__, __commit__)
version=setup_version("my_package"),
...
)
Repository structure
setuptools_us4us/versioning.py: git-based version numbers (get_version,get_version_for_release_branch,find_parent_release_branch):- tagged commit
va.b.cor release candidateva.b.c-rcN->a.b.c(a release candidate wheel file is built with the final version number), - release branch
va.b.x->a.b.(c+1).devYYYYMMDD, - feature branch -> parent release branch version + branch name as local
label, e.g.
0.7.0.dev20260823+ref.mvandv.194. - release candidate tags are not taken into account when determining the next dev version.
- tagged commit
setuptools_us4us/setup_helpers.py: helpers forsetup.py(setup_version,write_version_file,read_version_file,is_dev_version).setuptools_us4us/cmd.py: running shell commands (run_cmd).
Metadata
Release files for setuptools-us4us 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| setuptools_us4us-0.1.1.tar.gz | 7.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| setuptools_us4us-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.7 kB
Release files / setuptools_us4us-0.1.1.tar.gz
| Download URL | setuptools_us4us-0.1.1.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bec7cb4dacc1de3aba1586de9f115fc7e4cc11fa74b2d8f6f4759a2485399fbf
|
|
BLAKE2b-256 checksum How to use checksums |
64096a3554a66ea1d172be4ed3689d5ab4c3326856ade036827976eafae5fd2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.16
|
Release files / setuptools_us4us-0.1.1-py3-none-any.whl
| Download URL | setuptools_us4us-0.1.1-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ae51f7fb3dd0d0e305b48ca41f23a6cc96d3e5bd7a8672b8059e538a6720d464
|
|
BLAKE2b-256 checksum How to use checksums |
58d360ea3cfe0a8c48448b85978d839e696552ae005ae51c13a8791cef3bf49d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.16
|
Security for setuptools-us4us 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.