Skip to main content

Getting Started

Installation

pip install capo-lex-runtime-v2

Usage

from capo_lex_runtime_v2 import AsyncLexRuntimeV2Client


async def main():
    async with AsyncLexRuntimeV2Client() as lex_runtime_v2:
        # Example: call the delete_session operation
        response = await lex_runtime_v2.delete_session()
        print(response["bot_id"])

Streaming Request

Some operations accept a streaming request body. Pass an async iterator of bytes chunks, or the whole body as bytes, for the streaming parameter.

A plain iterator can be sent only once, so if a request fails after its body was transmitted the operation is not retried. To get retries for streamed uploads, pass a Body instead: it wraps a source that can be reopened, and every attempt streams a fresh copy. Body.from_path (sync client) and Body.async_from_path (async client, needs anyio) stream a file from disk; Body(opener) takes any context manager that yields a (stream, length) pair.

from capo_lex_runtime_v2 import AsyncLexRuntimeV2Client, Body


async def main():
    async with AsyncLexRuntimeV2Client() as lex_runtime_v2:
        # Example: call recognize_utterance with a streaming request body
        async def chunks():
            yield b'Hello, World!'

        response = await lex_runtime_v2.recognize_utterance(input_stream=chunks())
        print(response)

        # Or pass the whole body as bytes
        response = await lex_runtime_v2.recognize_utterance(input_stream=b'Hello, World!')
        print(response)

        # Or stream a file with Body: the file is reopened on every retry
        # and Content-Length is taken from its size, so no content_length needed
        response = await lex_runtime_v2.recognize_utterance(input_stream=Body.async_from_path("hello.txt"))
        print(response)

Streaming Response

Some operations return a streaming response body. Use the operation as an async context manager and iterate over the response field to read chunks.

from capo_lex_runtime_v2 import AsyncLexRuntimeV2Client


async def main():
    async with AsyncLexRuntimeV2Client() as lex_runtime_v2:
        # Example: call put_session and read the streaming response
        async with lex_runtime_v2.put_session() as response:
            async for chunk in response["audio_stream"]:
                print(chunk)

Error Handling

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

from capo_lex_runtime_v2 import AsyncLexRuntimeV2Client
from capo_lex_runtime_v2.error import AccessDeniedException


async def main():
    async with AsyncLexRuntimeV2Client() as lex_runtime_v2:
        try:
            await lex_runtime_v2.delete_session()
        except AccessDeniedException 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_lex_runtime_v2 import AsyncLexRuntimeV2Client


async def main():
    async with AsyncLexRuntimeV2Client() as lex_runtime_v2:
        # Default: 3 attempts for every operation
        response = await lex_runtime_v2.delete_session()

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

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

Metadata

Release files for capo-lex-runtime-v2 0.5.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-lex-runtime-v2 0.5.0
File Size Uploaded Provenance
capo_lex_runtime_v2-0.5.0.tar.gz 88.6 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-lex-runtime-v2 0.5.0
File Interpreter ABI Platform
capo_lex_runtime_v2-0.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 237.5 kB

Release files / capo_lex_runtime_v2-0.5.0.tar.gz

Download URL capo_lex_runtime_v2-0.5.0.tar.gz
Size 88.6 kB
Tags Source
SHA-256 checksum
How to use checksums
6d72624bccfe0cb9cb9e9c53879c4666e31472b5cd92157c9e8638d25b54b009
BLAKE2b-256 checksum
How to use checksums
3b14e5e5339881d649750bad418c544fdb21f7f2959ea772ff684b59c76602ff
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_lex_runtime_v2-0.5.0-py3-none-any.whl

Download URL capo_lex_runtime_v2-0.5.0-py3-none-any.whl
Size 148.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
20360ab3680157bc22e0dc668f5dfac094fe4f424ead5588f1239af2946d6cbd
BLAKE2b-256 checksum
How to use checksums
975cf7e66d5b9aafb8447c4b80b26f1eedb542f45ddb695f107d8017c00afcc7
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-lex-runtime-v2 0.5.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