Introduction
This project provides a Python 2.7/3.x library to aid checking strings in files. Verace’s main use case is checking that version strings are consistent in project files. The main features of this library are:
Custom parse any project files for strings.
Easily determine if all strings are consistent.
Quickly updated tracked strings.
Should work on any platform without additional dependencies; Qprompt is recommended for default prompts.
Status
Currently, this project is in the development release stage. While this project is suitable for use, please note that there may be incompatibilities in new releases.
Requirements
Verace should run on any Python 2.7/3.x interpreter without additional dependencies.
Installation
Verace can be installed with pip using the following command: pip install verace
Additional, Verace can be installed from source by running: python setup.py install
Usage
Start by importing Verace into your Python script:
import verace
Create a VerChecker object, name it and set the root location:
mychk = verace.VerChecker("My Checker", __file__)
Include a file to check. If no check function is provided, check_basic() will be used by default. Let’s look for the version string in setup.py:
mychk.include(r"lib\setup.py", match="version = ", splits=[('"',1)])
Get the string found by the checker:
print("version found = " + mychk.string())
# version found = 0.4.1
The string can be updated in all associated files:
mychk.update("something different!")
That’s the basics. Check out the documentation for more info.
Here are some real-world examples of Verace in action:
Documentation
The full documentation for this project can be found here on Read the Docs.
FAQ
How is Verace pronounced?
“ver-AH-che” - Italian word for “truthful/accurate”.
Is this library only for Python projects?
Not at all! Any project can use Verace!
Metadata
Release files for verace 0.4.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 | |
|---|---|---|---|---|
| verace-0.4.1.tar.gz | 5.3 kB | Without provenance | Details |
Release files / verace-0.4.1.tar.gz
| Download URL | verace-0.4.1.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d6fcd07b24b6cbdfc10bde33e15b93c18a809c8542a5f3b183ec1ac01562b2b0
|
|
BLAKE2b-256 checksum How to use checksums |
9594346cfba93fbe62761e8eb1f4084a4d7f4acafe65055a05836dbad67da745
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for verace 0.4.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.