capo-pi: typed, async Python SDK for AWS PI
capo-pi is a typed Python SDK for AWS PI. It has an async client, AsyncPIClient, for asyncio and trio, and a sync client, PIClient, 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/pi/
Installation
pip install capo-pi
Usage
from capo_pi import AsyncPIClient
async def main():
async with AsyncPIClient() as pi:
# Example: call the create_performance_analysis_report operation
response = await pi.create_performance_analysis_report()
print(response["analysis_report_id"])
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_pi import AsyncPIClient
async def main():
async with AsyncPIClient() as pi:
# Example: paginate over describe_dimension_keys
async for item in pi.iter_describe_dimension_keys():
print(item)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_pi import AsyncPIClient
from capo_pi.error import InternalServiceError
async def main():
async with AsyncPIClient() as pi:
try:
await pi.create_performance_analysis_report()
except InternalServiceError 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_pi import AsyncPIClient
async def main():
async with AsyncPIClient() as pi:
# Default: 3 attempts for every operation
response = await pi.create_performance_analysis_report()
# Override per operation
response = await pi.create_performance_analysis_report(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await pi.create_performance_analysis_report(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-pi 0.10.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_pi-0.10.0.tar.gz | 99.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_pi-0.10.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 272.2 kB
Release files / capo_pi-0.10.0.tar.gz
| Download URL | capo_pi-0.10.0.tar.gz |
|---|---|
| Size | 99.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eb2e8cb50c7054152c89d6a3c66eefdaf3cf207ad4c911631ee0b80452904e23
|
|
BLAKE2b-256 checksum How to use checksums |
f26e980f373f62a6017bc4d9c7fdef8b07a922cf8e330439c7c53a1fe735b45d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","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_pi-0.10.0-py3-none-any.whl
| Download URL | capo_pi-0.10.0-py3-none-any.whl |
|---|---|
| Size | 172.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c7fa9b2c0f63e55626bdf8b075e97d8a0242b2e623d6aa2e82d4ab449570783e
|
|
BLAKE2b-256 checksum How to use checksums |
b5a64896bf3797732825902a4112a85dcd5ea2fd27cb60a50996d12dac08f33f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","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-pi 0.10.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.