Skip to main content

Getting Started

Installation

pip install capo-chime-sdk-media-pipelines

Usage

from capo_chime_sdk_media_pipelines import AsyncChimeSDKMediaPipelinesClient


async def main():
    async with AsyncChimeSDKMediaPipelinesClient() as chime_sdk_media_pipelines:
        # Example: call the create_media_capture_pipeline operation
        response = await chime_sdk_media_pipelines.create_media_capture_pipeline()
        print(response["media_capture_pipeline"])

Pagination

Some operations in this SDK support pagination. If the operation supports pagination it will have an iter_ prefixed method that returns an async iterator.

from capo_chime_sdk_media_pipelines import AsyncChimeSDKMediaPipelinesClient


async def main():
    async with AsyncChimeSDKMediaPipelinesClient() as chime_sdk_media_pipelines:
        # Example: paginate over list_media_capture_pipelines
        async for item in chime_sdk_media_pipelines.iter_list_media_capture_pipelines():
            print(item)

Error Handling

The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.

from capo_chime_sdk_media_pipelines import AsyncChimeSDKMediaPipelinesClient
from capo_chime_sdk_media_pipelines.error import BadRequestException


async def main():
    async with AsyncChimeSDKMediaPipelinesClient() as chime_sdk_media_pipelines:
        try:
            await chime_sdk_media_pipelines.create_media_capture_pipeline()
        except BadRequestException 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_chime_sdk_media_pipelines import AsyncChimeSDKMediaPipelinesClient


async def main():
    async with AsyncChimeSDKMediaPipelinesClient() as chime_sdk_media_pipelines:
        # Default: 3 attempts for every operation
        response = await chime_sdk_media_pipelines.create_media_capture_pipeline()

        # Override per operation
        response = await chime_sdk_media_pipelines.create_media_capture_pipeline(config_overrides={"retry_max_attempts": 5})

        # Disable retries for this call
        response = await chime_sdk_media_pipelines.create_media_capture_pipeline(config_overrides={"retry_max_attempts": 1})

Metadata

Release files for capo-chime-sdk-media-pipelines 0.3.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-chime-sdk-media-pipelines 0.3.0
File Size Uploaded Provenance
capo_chime_sdk_media_pipelines-0.3.0.tar.gz 126.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-chime-sdk-media-pipelines 0.3.0
File Interpreter ABI Platform
capo_chime_sdk_media_pipelines-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 441.5 kB

Release files / capo_chime_sdk_media_pipelines-0.3.0.tar.gz

Download URL capo_chime_sdk_media_pipelines-0.3.0.tar.gz
Size 126.2 kB
Tags Source
SHA-256 checksum
How to use checksums
f4850f8ef97b38a92a7e643bd1048536ac59503366eef0bd2c4e57dbfb7a1969
BLAKE2b-256 checksum
How to use checksums
238463a669303bb07c98c5d7068ab4c33e2d935f577dcaa3050dced594049753
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.18 {"installer":{"name":"uv","version":"0.12.18","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_chime_sdk_media_pipelines-0.3.0-py3-none-any.whl

Download URL capo_chime_sdk_media_pipelines-0.3.0-py3-none-any.whl
Size 315.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
aa4bf12e2c36742e447bfcd6e71509df9dcc2cbab28a27406861ea376f7c88e7
BLAKE2b-256 checksum
How to use checksums
aa9218c27a78b45fb9ab413abea9d778feb3e93ea17c57e3e128a85997bb35f8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.18 {"installer":{"name":"uv","version":"0.12.18","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-chime-sdk-media-pipelines 0.3.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.

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