A way to ensure critical libraries are up-to-date
The gitvck library is a CPython project which is designed to help ensure the latest version of a critical library is being used by your project.
Sometimes a project relies on the latest version of an underlying library. The gitvck library is designed to run in the background on program startup and check if the version of a critical library is the latest version available. If the critical library being imported is not the latest, the user is alerted that a later version is available. If the latest version is already being used, the test ends silently.
However, this is a notification-only service. The user is not prevented from carrying on.
If you have any questions that are not covered by this documentation, or if you spot any bugs, issues or have any recommendations, please feel free to contact us.
Installation
For most users, the easiest way is probably to install the latest version hosted on PyPI, after activating the appropriate virtual environment.
pip install gitvck
Using the Library
The documentation suite contains detailed explanation and example usage for each of the library's importable modules. For detailed documentation, usage examples and links the source code itself, please refer to the Library API page.
Quickstart
To demonstrate how easy it is to get up and running, the template below can be copied and pasted into your program's primary __init__.py module. When your program starts up, the __init__.py module is run, and performs the version check in the background.
To verify the version of a critical library against GitHub use:
from gitvck import gitvck
from <project>._version import __version__
gitvck.VersionCheck(name='project-spam',
source='git',
path='https://github.com/s3dev/project-spam',
version=__version__).test()
More example templates can be found in the gitvck module documentation page.
Sources
The following code configuration sources can be accessed by gitvck:
- PyPI
- GitHub
- Git (a local or remote repository, accessed through a filesystem)
Guidance for using these various sources can be found in the gitvck module documentation page.
Metadata
Release files for gitvck 2.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 | Actions |
|---|---|---|---|---|
| gitvck-2.1.1.tar.gz | 2.9 MB | Without provenance | Details for gitvck-2.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gitvck-2.1.1-py3-none-any.whl | Python 3 | none | any | Details for gitvck-2.1.1-py3-none-any.whl |
Total release size: 2.9 MB
Release files / gitvck-2.1.1.tar.gz
| Download URL | gitvck-2.1.1.tar.gz |
|---|---|
| Size | 2.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f96f9dd2872497ea5c5fea47a16fd11a7aa1a83c45241bf57e58e8344109303f
|
|
BLAKE2b-256 checksum How to use checksums |
1c208f079308df79b151e1a1d71dc2aa12660dcee819a35b2cf2729246528090
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.8
|
Release files / gitvck-2.1.1-py3-none-any.whl
| Download URL | gitvck-2.1.1-py3-none-any.whl |
|---|---|
| Size | 8.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dcbf0379b23708c64e7f31a068d801fea10b816763315278c5213f003e4c9e58
|
|
BLAKE2b-256 checksum How to use checksums |
a9b4f9c6d57ee38f9f22b0e0e40ea28ec9ec35d2af93b34fc89cc9b02ec2e072
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.8
|
Security for gitvck 2.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.