Skip to main content

Getting Started

Installation

pip install capo-account-access

Usage

from capo_account_access import AsyncAccountAccessClient


async def main():
    async with AsyncAccountAccessClient() as account_access:
        # Example: call the list_tags_for_resource operation
        response = await account_access.list_tags_for_resource()
        print(response["tags"])

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_access import AsyncAccountAccessClient


async def main():
    async with AsyncAccountAccessClient() as account_access:
        # Example: paginate over list_applications
        async for item in account_access.iter_list_applications():
            print(item)

Error Handling

The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.

from capo_account_access import AsyncAccountAccessClient
from capo_account_access.error import InternalServerException


async def main():
    async with AsyncAccountAccessClient() as account_access:
        try:
            await account_access.list_tags_for_resource()
        except InternalServerException 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_access import AsyncAccountAccessClient


async def main():
    async with AsyncAccountAccessClient() as account_access:
        # Default: 3 attempts for every operation
        response = await account_access.list_tags_for_resource()

        # Override per operation
        response = await account_access.list_tags_for_resource(config_overrides={"retry_max_attempts": 5})

        # Disable retries for this call
        response = await account_access.list_tags_for_resource(config_overrides={"retry_max_attempts": 1})

Metadata

Release files for capo-account-access 0.6.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-account-access 0.6.0
File Size Uploaded Provenance
capo_account_access-0.6.0.tar.gz 75.5 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-account-access 0.6.0
File Interpreter ABI Platform
capo_account_access-0.6.0-py3-none-any.whl Python 3 none any Details

Total release size: 199.6 kB

Release files / capo_account_access-0.6.0.tar.gz

Download URL capo_account_access-0.6.0.tar.gz
Size 75.5 kB
Tags Source
SHA-256 checksum
How to use checksums
4d442760ab8fd256ffe1db0b4d6c4372b34bdb1d38239e17af9df6a921011d14
BLAKE2b-256 checksum
How to use checksums
49a306f5b3c29ae4b2e60355f970552c19fdb7376fa1e5924f1d4045f87a7b97
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_access-0.6.0-py3-none-any.whl

Download URL capo_account_access-0.6.0-py3-none-any.whl
Size 124.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0f205d565ca88b8da3ed734fc3a5822b61b6a7d5356c5236292987aa0170ad70
BLAKE2b-256 checksum
How to use checksums
ce54a2f7e547eb1fbf825aca5898cd7dc23730b0509ff19a1e0d50f9dc1bb064
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-access 0.6.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.

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