Client to access to Beacon services.
Actually it provides:
- Synchronous sequencial client (
beaconclient.syncio.BeaconClient) - Asynchronous sequencial client (
beaconclient.asyncio.BeaconClient) - Sans I/O protocol (
beaconclient.protocol) to create other clients - Config helper (
beaconclient.config.read-config) to read ocnfig from file or beacon URIs.
Notice that the BLISS project provides it's own beacon client supporting the whole API with a non-seqnencial implementation.
Sync client
Client to access to configuration files, redis addresses, and stored keys.
from beaconclient.syncio import BeaconClient
client = BeaconClient()
redis_address = client.get_redis_db()
Async client
Async client to access to configuration files, redis addresses, and stored keys.
from beaconclient.asyncio import BeaconClient
client = BeaconClient()
redis_address = await client.get_redis_db()
Read configuration
Helper to read yaml configuration file.
from beaconclient.config import read_config
content = read_config("beacon:///path/to/file.yml")
content2 = read_config("file:///my_file.yml')
Metadata
Release files for beaconclient 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| beaconclient-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Release files / beaconclient-1.0.3-py3-none-any.whl
| Download URL | beaconclient-1.0.3-py3-none-any.whl |
|---|---|
| Size | 10.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
571013bc1c0f1975bcf2a1e5baf25e38cb757bbc52c6c9e5869d2b1b3938a31a
|
|
BLAKE2b-256 checksum How to use checksums |
f0f520fc8db1af16b664824c1cc61b8b6e7c5138f8c7f1cf3a6685c0ca8950b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.20
|
Security for beaconclient 1.0.3
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.