Getting Started
Installation
pip install capo-firehose
Usage
from capo_firehose import AsyncFirehoseClient
async def main():
async with AsyncFirehoseClient() as firehose:
# Example: call the create_delivery_stream operation
response = await firehose.create_delivery_stream()
print(response["delivery_stream_arn"])
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_firehose import AsyncFirehoseClient
from capo_firehose.error import InvalidArgumentException
async def main():
async with AsyncFirehoseClient() as firehose:
try:
await firehose.create_delivery_stream()
except InvalidArgumentException as e:
print(f"Error: {e}")
print(e.data) # additional error data
Retrying
The SDK retries failed operations automatically. Retry behaviour follows the Smithy specification: errors are retried based on their is_retryable and is_throttling_error attributes. Throttling errors use a longer base delay. Network-level failures (connection errors and timeouts) are also retried. Non-retryable errors, such as client errors without the @retryable trait, are raised immediately without further attempts.
The number of attempts defaults to 3 and can be changed at the client level via retry_max_attempts, or per call via config_overrides.
from capo_firehose import AsyncFirehoseClient
async def main():
async with AsyncFirehoseClient() as firehose:
# Default: 3 attempts for every operation
response = await firehose.create_delivery_stream()
# Override per operation
response = await firehose.create_delivery_stream(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await firehose.create_delivery_stream(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-firehose 0.4.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 | |
|---|---|---|---|---|
| capo_firehose-0.4.0.tar.gz | 151.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_firehose-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 473.6 kB
Release files / capo_firehose-0.4.0.tar.gz
| Download URL | capo_firehose-0.4.0.tar.gz |
|---|---|
| Size | 151.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0bfe1f9a6fa8a5e24de60cfa537e7ff082d7b0427fc83c2f8360ed76c2c4d249
|
|
BLAKE2b-256 checksum How to use checksums |
1f4d246cba681a995b8a5985854ce973120aeebe264cfc30d1a95fe1445c464e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / capo_firehose-0.4.0-py3-none-any.whl
| Download URL | capo_firehose-0.4.0-py3-none-any.whl |
|---|---|
| Size | 322.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a46591366601906c94b86bffb64264fe0bba0c11ec9f04e45e46f70268019427
|
|
BLAKE2b-256 checksum How to use checksums |
a398097eebeb9487f900d7b8b326f820d5f3b65217c5fabf67ab75b5e803a1f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for capo-firehose 0.4.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.