Skip to main content

Getting Started

Installation

pip install capo-dynamodb

Usage

from capo_dynamodb import AsyncDynamoDBClient


async def main():
    async with AsyncDynamoDBClient() as dynamo_db:
        # Example: call the batch_execute_statement operation
        response = await dynamo_db.batch_execute_statement()
        print(response["responses"])

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_dynamodb import AsyncDynamoDBClient


async def main():
    async with AsyncDynamoDBClient() as dynamo_db:
        # Example: paginate over list_contributor_insights
        async for item in dynamo_db.iter_list_contributor_insights():
            print(item)

Waiters

Waiters poll an operation until a resource reaches a desired state. If the operation supports waiters it will have a wait_until_ prefixed method.

from capo_dynamodb import AsyncDynamoDBClient


async def main():
    async with AsyncDynamoDBClient() as dynamo_db:
        # Example: wait for table_not_exists
        await dynamo_db.wait_until_table_not_exists(max_wait_time=300)

Error Handling

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

from capo_dynamodb import AsyncDynamoDBClient
from capo_dynamodb.error import InternalServerError


async def main():
    async with AsyncDynamoDBClient() as dynamo_db:
        try:
            await dynamo_db.batch_execute_statement()
        except InternalServerError 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_dynamodb import AsyncDynamoDBClient


async def main():
    async with AsyncDynamoDBClient() as dynamo_db:
        # Default: 3 attempts for every operation
        response = await dynamo_db.batch_execute_statement()

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

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

Metadata

Release files for capo-dynamodb 0.15.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-dynamodb 0.15.0
File Size Uploaded Provenance
capo_dynamodb-0.15.0.tar.gz 364.1 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-dynamodb 0.15.0
File Interpreter ABI Platform
capo_dynamodb-0.15.0-py3-none-any.whl Python 3 none any Details

Total release size: 1.1 MB

Release files / capo_dynamodb-0.15.0.tar.gz

Download URL capo_dynamodb-0.15.0.tar.gz
Size 364.1 kB
Tags Source
SHA-256 checksum
How to use checksums
f7c36414ac119eee5db3d25699b61ff4496bf15a0afd22f57f3ae0e72221bb3b
BLAKE2b-256 checksum
How to use checksums
9f22b3f5f1e949b672f0fe7fb975de2d550700e2a105b024928a9e0f263a2890
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_dynamodb-0.15.0-py3-none-any.whl

Download URL capo_dynamodb-0.15.0-py3-none-any.whl
Size 726.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
77d1754663ca00749aec202d0c5a69e1e219ebc5250d84b35a4d48bded628ba0
BLAKE2b-256 checksum
How to use checksums
46bf1b47c5ac272b7e513473bd707ebe5e70dd6f73158c7383cb1519a134415f
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-dynamodb 0.15.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