Automatically obtain the version number of the importer, retrieving it from
pkg_resources or source control if necessary.
Example:
# my fancy module
from __autoversion__ import __version__, __version_tuple__
Current support:
Git
1 maintainer
Metadata
1 maintainer
Release files for autoversion 1.2.2
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 | |
|---|---|---|---|---|
| autoversion-1.2.2.tar.gz | 2.9 kB | Without provenance | Details |
Release files / autoversion-1.2.2.tar.gz
| Download URL | autoversion-1.2.2.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1beda2277a208524c96d50d09c8dc31f53316b55fde7803e8ee60ac4a7d28c14
|
|
BLAKE2b-256 checksum How to use checksums |
fbc2b08b0418a2c6d61b433d5b7bcc4291eb62f0fa1d0edc1cd11f385db1c1e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for autoversion 1.2.2
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.
