capo-account: typed, async Python SDK for AWS Account
capo-account is a typed Python SDK for AWS Account. It has an async client, AsyncAccountClient, for asyncio and trio, and a sync client, AccountClient, 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/account/
Installation
pip install capo-account
Usage
from capo_account import AsyncAccountClient
async def main():
async with AsyncAccountClient() as account:
# Example: call the put_account_name operation
response = await account.put_account_name()
print(response)
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_account import AsyncAccountClient
async def main():
async with AsyncAccountClient() as account:
# Example: paginate over list_regions
async for item in account.iter_list_regions():
print(item)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_account import AsyncAccountClient
from capo_account.error import AccessDeniedException
async def main():
async with AsyncAccountClient() as account:
try:
await account.put_account_name()
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_account import AsyncAccountClient
async def main():
async with AsyncAccountClient() as account:
# Default: 3 attempts for every operation
response = await account.put_account_name()
# Override per operation
response = await account.put_account_name(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await account.put_account_name(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-account 0.12.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_account-0.12.0.tar.gz | 93.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_account-0.12.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 265.3 kB
Release files / capo_account-0.12.0.tar.gz
| Download URL | capo_account-0.12.0.tar.gz |
|---|---|
| Size | 93.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1194791f286cc08ef9edc8095b97dcf4d84321cb0dc9cbe77ef05309afa3503b
|
|
BLAKE2b-256 checksum How to use checksums |
92db2bea73844c1519eaccae6defc87cfa980f642ea4ce82979202d249f71b4d
|
| 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_account-0.12.0-py3-none-any.whl
| Download URL | capo_account-0.12.0-py3-none-any.whl |
|---|---|
| Size | 171.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c65e53f228d22d5bd5eb7740d1d65e3d26589350992b0481bfecb25e5d088ed1
|
|
BLAKE2b-256 checksum How to use checksums |
d9bf8d431d7ea0582e955f638d37ccab0426603a315f3e5a52ac1dbaee2830cd
|
| 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-account 0.12.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.