Skip to main content

Ingot H2 Ingot package.

Provides supporting HTTP/2 protocol via integration with the hyper h2 package.

https://python-hyper.org/projects/h2/en/stable/index.html https://datatracker.ietf.org/doc/html/rfc7540

For consumers

For using the Ingot package just execute the following commands:

  • Add the package to the requirements.txt file of your project.
  • Install int using the pip tool.
  • TODO. Add here something extra information.

Package CLI

The package provides CLI. It allows 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-h2-cli <command>

Getting package CLI help:

ingot-h2-cli --help
ingot-h2-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-h2.git
cd ingot-h2

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_h2.scripts.ingot_h2 ...

Metadata

Release files for ingot-h2 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ingot-h2 0.1.0
File Size Uploaded Provenance
ingot-h2-0.1.0.tar.gz 10.5 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for ingot-h2 0.1.0
File Interpreter ABI Platform
ingot_h2-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 21.9 kB

Release files / ingot-h2-0.1.0.tar.gz

Download URL ingot-h2-0.1.0.tar.gz
Size 10.5 kB
Tags Source
SHA-256 checksum
How to use checksums
190c976ec474171cbe8311049f4cc75e642d74205f3d860f26aa7a42678fcc2e
BLAKE2b-256 checksum
How to use checksums
259a71b85aba83983e5d44d80dd7a902fb7bb26481f9ee4dd0e26da7a691d1df
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.2

Release files / ingot_h2-0.1.0-py3-none-any.whl

Download URL ingot_h2-0.1.0-py3-none-any.whl
Size 11.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4d91b2f7d7bffc54751db940dbfbc81156f973d42ceb0d7f7342195d3adf69ff
BLAKE2b-256 checksum
How to use checksums
7a80988147e238a59e532347bd2773e4cf81336a8d0254d442389218a3a5591f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.2

Security for ingot-h2 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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page