Getting Started
Installation
pip install capo-lex-runtime-service
Usage
from capo_lex_runtime_service import AsyncLexRuntimeServiceClient
async def main():
async with AsyncLexRuntimeServiceClient() as lex_runtime_service:
# Example: call the delete_session operation
response = await lex_runtime_service.delete_session()
print(response["bot_name"])
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_service import AsyncLexRuntimeServiceClient, Body
async def main():
async with AsyncLexRuntimeServiceClient() as lex_runtime_service:
# Example: call post_content with a streaming request body
async def chunks():
yield b'Hello, World!'
response = await lex_runtime_service.post_content(input_stream=chunks())
print(response)
# Or pass the whole body as bytes
response = await lex_runtime_service.post_content(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_service.post_content(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_service import AsyncLexRuntimeServiceClient
async def main():
async with AsyncLexRuntimeServiceClient() as lex_runtime_service:
# Example: call post_content and read the streaming response
async with lex_runtime_service.post_content() 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_service import AsyncLexRuntimeServiceClient
from capo_lex_runtime_service.error import BadRequestException
async def main():
async with AsyncLexRuntimeServiceClient() as lex_runtime_service:
try:
await lex_runtime_service.delete_session()
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_lex_runtime_service import AsyncLexRuntimeServiceClient
async def main():
async with AsyncLexRuntimeServiceClient() as lex_runtime_service:
# Default: 3 attempts for every operation
response = await lex_runtime_service.delete_session()
# Override per operation
response = await lex_runtime_service.delete_session(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await lex_runtime_service.delete_session(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-lex-runtime-service 0.3.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_lex_runtime_service-0.3.0.tar.gz | 83.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_lex_runtime_service-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 210.2 kB
Release files / capo_lex_runtime_service-0.3.0.tar.gz
| Download URL | capo_lex_runtime_service-0.3.0.tar.gz |
|---|---|
| Size | 83.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3117c2c48ef67cd4d00bd4fd7ee6b2718e5588958acf6b9dd5d7d9df20372ccd
|
|
BLAKE2b-256 checksum How to use checksums |
3abbf45445d3098126bb2dd302c75892b3963a41cbfe7e4659156c244e1e17f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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_service-0.3.0-py3-none-any.whl
| Download URL | capo_lex_runtime_service-0.3.0-py3-none-any.whl |
|---|---|
| Size | 127.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
83fd9e54cc97dbcda96bda184ffe0573cd14dd55a9c34c543b23e44756597c50
|
|
BLAKE2b-256 checksum How to use checksums |
0e6cf728f027ec438df540f59bda5d4c4383e1e934b4ff4914dcd790be2cadba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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-service 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.