capo-personalize-events: typed, async Python SDK for AWS Personalize Events
capo-personalize-events is a typed Python SDK for AWS Personalize Events. It has an async client, AsyncPersonalizeEventsClient, for asyncio and trio, and a sync client, PersonalizeEventsClient, 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-events/
Installation
pip install capo-personalize-events
Usage
from capo_personalize_events import AsyncPersonalizeEventsClient
async def main():
async with AsyncPersonalizeEventsClient() as personalize_events:
# Example: call the put_action_interactions operation
response = await personalize_events.put_action_interactions()
print(response)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_personalize_events import AsyncPersonalizeEventsClient
from capo_personalize_events.error import InvalidInputException
async def main():
async with AsyncPersonalizeEventsClient() as personalize_events:
try:
await personalize_events.put_action_interactions()
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_events import AsyncPersonalizeEventsClient
async def main():
async with AsyncPersonalizeEventsClient() as personalize_events:
# Default: 3 attempts for every operation
response = await personalize_events.put_action_interactions()
# Override per operation
response = await personalize_events.put_action_interactions(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await personalize_events.put_action_interactions(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-personalize-events 0.9.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_personalize_events-0.9.0.tar.gz | 64.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_personalize_events-0.9.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 154.9 kB
Release files / capo_personalize_events-0.9.0.tar.gz
| Download URL | capo_personalize_events-0.9.0.tar.gz |
|---|---|
| Size | 64.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dd645ba8e4d92c85392365d71dc592a3a1843f00466eb399f7c0577e252583ac
|
|
BLAKE2b-256 checksum How to use checksums |
d1b1557a9c704226ff9f2bbbfed4851972cb30b1f79b5b44982244ca7d2a8195
|
| 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_events-0.9.0-py3-none-any.whl
| Download URL | capo_personalize_events-0.9.0-py3-none-any.whl |
|---|---|
| Size | 90.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7569065d0adc7910d1e6d34f81e97a35a7772ccf151f49a027a4478ecea44d65
|
|
BLAKE2b-256 checksum How to use checksums |
8584ab3ec78c69861d653ddce87f007263f2a555b35bf604ebac928ef24b8284
|
| 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-events 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.