Skip to main content

Getting Started

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.10.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-backup 0.10.0
File Size Uploaded Provenance
capo_backup-0.10.0.tar.gz 307.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-backup 0.10.0
File Interpreter ABI Platform
capo_backup-0.10.0-py3-none-any.whl Python 3 none any Details

Total release size: 1.1 MB

Release files / capo_backup-0.10.0.tar.gz

Download URL capo_backup-0.10.0.tar.gz
Size 307.2 kB
Tags Source
SHA-256 checksum
How to use checksums
8b95e5856bc3db077353214e35e2bfd3b24e2c8876054a29e0cc737c0d7ef832
BLAKE2b-256 checksum
How to use checksums
3b993d9864e8e44f02c780a351ba583eed6c2e2d00e2fff50526ca9f5f5054f0
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_backup-0.10.0-py3-none-any.whl

Download URL capo_backup-0.10.0-py3-none-any.whl
Size 752.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bfc7c5bae3c073b7d11029d423a103222f512f16eb0ba5863f645a1aae3b53c5
BLAKE2b-256 checksum
How to use checksums
cb8efa333586261294ee50a59c1ee97f2843882e8eb06e9d3a3d26ba10253a28
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-backup 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.

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