Ingot Tcp Ingot package.
Provides TCP functionality for Ingots projects
For consumers
For using the Ingot package just execute the following command:
pip install ingot_tcp
Of course, need to activate a destination virtual environment:
source .venv/bin/activate
... or to create it, if it hasn't prepared yet:
python3 -m venv .venv
Bootstrap
The Ingot package provides the Bootstrap CLI tool.
It allows to get started with the Ingot package quickly.
It generates the following skeletons:
TODO. Add builders here after generating theirs by the ingots package_bootstrap tool.
For using the CLI tool just call the following command:
ingot-tcp <command> --name=<entity_name> --description="The <entity> brief description."
Getting help:
ingot-tcp --help
ingot-tcp <command> --help
For developers
Prepare the project for working
Clone a repository:
mkdir ingots-libs
cd ingots-libs
git clone https://github.com/<path>/ingot_tcp.git
cd ingot_tcp
Prepare a virtual environment:
python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
Prepare repository hooks
pip install pre_commit
pre-commit install
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. Set the {NAME}_VERSION_SUFFIX virtual variable for specify package suffix.
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 bootstrap locally
Obviously, it's impossible to call the package bootstrap tool via package entry-point.
Use the following command instead:
python -m ingot_tcp.scripts.ingot_tcp ...
Metadata
Release files for ingot-tcp 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-tcp-0.1.0.tar.gz | 6.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ingot_tcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.7 kB
Release files / ingot-tcp-0.1.0.tar.gz
| Download URL | ingot-tcp-0.1.0.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
962c3df8ec9ce2019c2ec8120b615c35cf16dba20030e69aeb5f9cd5a5fd6b7f
|
|
BLAKE2b-256 checksum How to use checksums |
e88abf91203db7a7f6906e5a2a0b77818b6a7b3b65e7204d954e44cccde3dd51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/51.3.3 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.8.2
|
Release files / ingot_tcp-0.1.0-py3-none-any.whl
| Download URL | ingot_tcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a8a1bf8846826f96091ddf5620301f88c2de44b5c79b4fb80e0ec039de79dd89
|
|
BLAKE2b-256 checksum How to use checksums |
6037cc6b81aa77585a752497625f1595a95e04030bcc495222e18f376d205d0c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/51.3.3 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.8.2
|
Security for ingot-tcp 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.