bad-setuptools-git-version
Automatically set package version from Git. This is a re-release of [bad-setuptools-git-version][] with fixes and improvements, which is itself a re-release of setuptools-git-version
Introduction
Instead of hard-coding the package version in setup.py like:
setup(
name='foobar',
version='1.0.0',
...
)
this package allows to extract it from tags in the underlying Git repository:
setup(
name='foobar',
version_config={
"version_format": "{tag}.{cc}",
"starting_version": "0.1.0"
},
setup_requires=['bad-setuptools-git-version'],
...
)
The tool uses the semantically-latest tag as the base version. If there are no annotated tags, the version specified by starting_version will be used. If HEAD is at the tag, the version will be the tag itself. If there are commits ahead of the tag, the first 8 characters of the sha of the HEAD commit will be included.
1 maintainer
Metadata
1 maintainer
Release files for bad-setuptools-git-version 1.0.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bad_setuptools_git_version-1.0.12-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Release files / bad_setuptools_git_version-1.0.12-py2.py3-none-any.whl
| Download URL | bad_setuptools_git_version-1.0.12-py2.py3-none-any.whl |
|---|---|
| Size | 3.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
601ff8dbe019caab9cf9156d38d57ffa854c06390a9c44c54f73014d32f39b8c
|
|
BLAKE2b-256 checksum How to use checksums |
c75131df0c362abe4d815ec6c5a714383d257b350a7a6edb0d57dd18caebfc5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.7
|
Security for bad-setuptools-git-version 1.0.12
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.
