SemVerPy
Bumping versions. Semantically.
Usage is pretty simple:
>>> from semverpy import SemVerPy
>>> version = SemVerPy('1.0.0')
>>> version.bump_minor()
<SemVerPy(1.1.0)>
>>> str(version)
'1.1.0'
It also supports comparisons:
>>> version == SemVerPy('1.1.0')
True
>>> version > SemVerPy('1.0.0')
True
>>> version > SemVerPy('2.0.0')
False
When you bump a version, all the smaller version numbers are set to zeroes.
>>> version.bump_major()
<SemVerPy(2.0.0)>
>>> str(version)
'2.0.0'
You can also define a build number when bumping a version:
>>> version.bump_minor('buildinfo')
<SemVerPy(2.1.0-buildinfo)>
>>> str(version)
'2.1.0-buildinfo'
Lastly, if you define a partial version, you can be used as a dependency.
>>> version.satisfies(SemVerPy('2.0'))
False
>>> version.satisfies(SemVerPy('2.1'))
True
>>> version.satisfies(SemVerPy('2'))
True
>>> version == SemVerPy('2.1')
False
Metadata
Release files for SemVerPy 0.1.0
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 | |
|---|---|---|---|---|
| SemVerPy-0.1.0.tar.gz | 2.8 kB | Without provenance | Details |
Release files / SemVerPy-0.1.0.tar.gz
| Download URL | SemVerPy-0.1.0.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed7679448fa155ee664d8a2f9fd435c44775d3b9e19b873375b7364a47c336e4
|
|
BLAKE2b-256 checksum How to use checksums |
66212f992a5158cb0b4d5db9c65d4ab7db681a704272cf2cac1ec4948c2ee8cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for SemVerPy 0.1.0
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.