Ingot Grpclib Ingot package.
Provides gRPC functionality based on the grpclib package
For consumers
For using the Ingot package just execute the following commands:
- Add the package to the
requirements.txtfile of your project. - Install int using the
piptool. - TODO. Add here something extra information.
Package CLI
The package provides CLI.
It allows to start working with the package quickly.
It contains the following commands:
TODO. Add builders here after generating their by the ingots package_bootstrap tool.
For using the CLI tool just call the following command:
ingot-grpclib-cli <command>
Getting package CLI help:
ingot-grpclib-cli --help
ingot-grpclib-cli <command> --help
For developers
Prepare the project for working
Clone a repository:
mkdir ingots-libs
cd ingots-libs
git clone https://github.com/ABKorotky/ingot-grpclib
cd ingot-grpclib
Prepare a virtual environment:
python3.9 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
Prepare repository hooks
pip install pre_commit
pre-commit install
pre-commit autoupdate
Configure code-quality tools:
pip install black flake8 mypy coverage
Configure the Sphinx tool
Please, use the following page for configuring the Sphinx documentation generator: Sphinx
pip install sphinx
sphinx-build -b html docs docs/build -v
Using the tox tool
The Ingot package allows automation via the tox tool.
pip install tox
Use configured tox tool for several activities.
tox -e reformat - auto reformat code by the black tool, makes ordering import too.
tox -e cs - checks code style by PEP8.
tox -e ann - checks annotations of types by the mypy tool.
tox -e utc - runs unittests with the coverage tool.
tox -e report - builds coverage report for the project.
tox -e doc - builds a package documentation.
tox -e build - builds a package form current branch / tag / commit.
tox -e upload - uploads package to the PyPI index. Set the PYPI_REPOSITORY_ALIAS virtual variable for specify PyPI destination.
Calling tox without parameters will execute the following steps: cs, ann, utc and report.
Using package CLI locally
Obviously, it's impossible to call the package CLI via package entry-point.
Use the following command instead:
python -m ingot_grpclib.scripts.ingot_grpclib ...
Metadata
Release files for ingot-grpclib 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 | |
|---|---|---|---|---|
| ingot-grpclib-0.1.0.tar.gz | 10.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ingot_grpclib-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.0 kB
Release files / ingot-grpclib-0.1.0.tar.gz
| Download URL | ingot-grpclib-0.1.0.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bc5a39adf4402989f6259c72a49ff1785071cb05db37e3f165762d56318094dd
|
|
BLAKE2b-256 checksum How to use checksums |
492ef3d4e619ddd2157b908e5db00462dcd032cb6c45cc29d4253753e3714f99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.4 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.0 CPython/3.9.2
|
Release files / ingot_grpclib-0.1.0-py3-none-any.whl
| Download URL | ingot_grpclib-0.1.0-py3-none-any.whl |
|---|---|
| Size | 11.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
296fbb4818029fab3097c80f107a088a796b1523af194e386e67250057fccfe7
|
|
BLAKE2b-256 checksum How to use checksums |
9f995942c3defaf8e530ba3a72222e31dee2f4505e4e3de3971d0ca12b45b3c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.4 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.0 CPython/3.9.2
|
Security for ingot-grpclib 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.