This release is a pre-release and may not be stable for production use.
Library for generating signature keys and signing messages using nilVM and nilDB.
Description and Purpose
This library provides client-side functions that interact with nilVM and nilDB clusters to perform signature key generation and message signing.
Installation and Usage
The library can be imported in the usual ways:
import nilsig
from nilsig import *
Example
An example workflow that demonstrates use of the library is presented below:
import nilsig
Development
All installation and development dependencies are fully specified in pyproject.toml. The project.optional-dependencies object is used to specify optional requirements for various development tasks. This makes it possible to specify additional options (such as docs, lint, and so on) when performing installation using pip:
python -m pip install ".[docs,lint]"
Documentation
The documentation can be generated automatically from the source files using Sphinx:
python -m pip install ".[docs]"
cd docs
sphinx-apidoc -f -E --templatedir=_templates -o _source .. && make html
Testing and Conventions
All unit tests are executed and their coverage is measured when using pytest (see the pyproject.toml file for configuration details):
python -m pip install ".[test]"
python -m pytest
The subset of the unit tests included in the module itself and can be executed using doctest:
python src/nilsig/nilsig.py -v
Style conventions are enforced using Pylint:
python -m pip install ".[lint]"
python -m pylint src/nilsig
Contributions
In order to contribute to the source code, open an issue or submit a pull request on the GitHub page for this library.
Versioning
The version number format for this library and the changes to the library associated with version number increments conform with Semantic Versioning 2.0.0.
Publishing
This library can be published as a package on PyPI via the GitHub Actions workflow found in .github/workflows/build-publish-sign-release.yml that follows the recommendations found in the Python Packaging User Guide.
Ensure that any links in this README document to the Read the Docs documentation of this package (or its dependencies) have appropriate version numbers. Also ensure that the Read the Docs project for this library has an automation rule that activates and sets as the default all tagged versions.
Release files for nilsig 0.0.0a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nilsig-0.0.0a1.tar.gz | 8.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nilsig-0.0.0a1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.4 kB
Release files / nilsig-0.0.0a1.tar.gz
| Download URL | nilsig-0.0.0a1.tar.gz |
|---|---|
| Size | 8.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e8e5380ec87d0295e17b219df345501729e158de290cb75c2c1ea5b7542c142f
|
|
BLAKE2b-256 checksum How to use checksums |
a5bf44b5ba1ed4f1daeddabc2b9073d649835d11852c21070a59c5073f47a3ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 17, 2025.
Transparency logRelease files / nilsig-0.0.0a1-py3-none-any.whl
| Download URL | nilsig-0.0.0a1-py3-none-any.whl |
|---|---|
| Size | 8.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f1a3f58e5878abb2a11c10fda12311a16283a57910b4528f6526eb1742dba6b
|
|
BLAKE2b-256 checksum How to use checksums |
a01374d203d1dd7012e20d4587deaf40ccd6fdefaf66042fd3ed10a281dfe00f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 17, 2025.
Transparency log