capo-backup: typed, async Python SDK for AWS Backup
capo-backup is a typed Python SDK for AWS Backup. It has an async client, AsyncBackupClient, for asyncio and trio, and a sync client, BackupClient, 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/backup/
Installation
pip install capo-backup
Usage
from capo_backup import AsyncBackupClient
async def main():
async with AsyncBackupClient() as backup:
# Example: call the associate_backup_vault_mpa_approval_team operation
response = await backup.associate_backup_vault_mpa_approval_team()
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_backup import AsyncBackupClient
async def main():
async with AsyncBackupClient() as backup:
# Example: paginate over list_backup_access_points
async for item in backup.iter_list_backup_access_points():
print(item)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_backup import AsyncBackupClient
from capo_backup.error import InvalidParameterValueException
async def main():
async with AsyncBackupClient() as backup:
try:
await backup.associate_backup_vault_mpa_approval_team()
except InvalidParameterValueException 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_backup import AsyncBackupClient
async def main():
async with AsyncBackupClient() as backup:
# Default: 3 attempts for every operation
response = await backup.associate_backup_vault_mpa_approval_team()
# Override per operation
response = await backup.associate_backup_vault_mpa_approval_team(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await backup.associate_backup_vault_mpa_approval_team(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-backup 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_backup-0.12.0.tar.gz | 308.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_backup-0.12.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.1 MB
Release files / capo_backup-0.12.0.tar.gz
| Download URL | capo_backup-0.12.0.tar.gz |
|---|---|
| Size | 308.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ae49184a6fba34590f25c7186c5e2961092778a6561c7f6f8efb87da0c1875d9
|
|
BLAKE2b-256 checksum How to use checksums |
ae4e0e57f2334ad53f5821f619e59a511fe9a8a32061592ded133893cb1c4f11
|
| 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_backup-0.12.0-py3-none-any.whl
| Download URL | capo_backup-0.12.0-py3-none-any.whl |
|---|---|
| Size | 751.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9bebf93af31e0ec54793907be7a675b83960cdce3a4367945e26b483ab44531a
|
|
BLAKE2b-256 checksum How to use checksums |
2c77f94b87dfc06f5fd5a58bad9dd3590bc716d468d21b7d3dc8403518d57a7c
|
| 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-backup 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.