Skip to main content

capo-personalize-runtime: typed, async Python SDK for AWS Personalize Runtime

capo-personalize-runtime is a typed Python SDK for AWS Personalize Runtime. It has an async client, AsyncPersonalizeRuntimeClient, for asyncio and trio, and a sync client, PersonalizeRuntimeClient, with the same methods. Requests and responses are typed with TypedDicts, so your editor and type checker know every field.

It is part of capo, a community-driven alternative to boto3 and aioboto3, built on its own HTTP stack instead of botocore and generated from the official AWS Smithy models. Documentation: https://capo-sdk.dev/services/personalize-runtime/

Installation

pip install capo-personalize-runtime

Usage

from capo_personalize_runtime import AsyncPersonalizeRuntimeClient


async def main():
    async with AsyncPersonalizeRuntimeClient() as personalize_runtime:
        # Example: call the get_action_recommendations operation
        response = await personalize_runtime.get_action_recommendations()
        print(response["action_list"])

Error Handling

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

from capo_personalize_runtime import AsyncPersonalizeRuntimeClient
from capo_personalize_runtime.error import InvalidInputException


async def main():
    async with AsyncPersonalizeRuntimeClient() as personalize_runtime:
        try:
            await personalize_runtime.get_action_recommendations()
        except InvalidInputException 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_personalize_runtime import AsyncPersonalizeRuntimeClient


async def main():
    async with AsyncPersonalizeRuntimeClient() as personalize_runtime:
        # Default: 3 attempts for every operation
        response = await personalize_runtime.get_action_recommendations()

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

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

Metadata

Release files for capo-personalize-runtime 0.9.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-personalize-runtime 0.9.0
File Size Uploaded Provenance
capo_personalize_runtime-0.9.0.tar.gz 66.0 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-personalize-runtime 0.9.0
File Interpreter ABI Platform
capo_personalize_runtime-0.9.0-py3-none-any.whl Python 3 none any Details

Total release size: 156.5 kB

Release files / capo_personalize_runtime-0.9.0.tar.gz

Download URL capo_personalize_runtime-0.9.0.tar.gz
Size 66.0 kB
Tags Source
SHA-256 checksum
How to use checksums
a28a7650a4bba48f90e0e15eb66555c0d7047a6843633985e733ee45f92794da
BLAKE2b-256 checksum
How to use checksums
8a119bd71044254a70aa8929731a8507e8059b5a59c250f3300744ef5c307f67
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","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_personalize_runtime-0.9.0-py3-none-any.whl

Download URL capo_personalize_runtime-0.9.0-py3-none-any.whl
Size 90.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8fe7c5a87e29c14afbbe9793a1815cca7b3c23f19462556aee363b7fd409a676
BLAKE2b-256 checksum
How to use checksums
e52e8088b4080dc27cca16862ca0c895e008b86a90b7896997b1b8cd4d2b1979
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","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-personalize-runtime 0.9.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