Skip to main content

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.2.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 capo-firehose 0.2.0
File Size Uploaded Provenance
capo_firehose-0.2.0.tar.gz 151.4 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-firehose 0.2.0
File Interpreter ABI Platform
capo_firehose-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 473.5 kB

Release files / capo_firehose-0.2.0.tar.gz

Download URL capo_firehose-0.2.0.tar.gz
Size 151.4 kB
Tags Source
SHA-256 checksum
How to use checksums
7394751f999a8523efab01bb858fc66f6238852faf3296426f0b7d48da571fdf
BLAKE2b-256 checksum
How to use checksums
421cb5f4f1261681b162e5cb31e7e6426e925dc599d9257ad45b300a1c2b15ef
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.21 {"installer":{"name":"uv","version":"0.12.21","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.2.0-py3-none-any.whl

Download URL capo_firehose-0.2.0-py3-none-any.whl
Size 322.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a944fecc3953bd796678230d236a149275f0d8285f3a431e90c5cdb18860baee
BLAKE2b-256 checksum
How to use checksums
027b3c3fea67eedfdfe59bb0e580f5142a9387e4403ff931ecab4a93a6ccf2c3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.21 {"installer":{"name":"uv","version":"0.12.21","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.2.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.

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