Skip to main content

capo-sesv2: typed, async Python SDK for AWS Sesv2

capo-sesv2 is a typed Python SDK for AWS Sesv2. It has an async client, AsyncSESv2Client, for asyncio and trio, and a sync client, SESv2Client, 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/sesv2/

Installation

pip install capo-sesv2

Usage

from capo_sesv2 import AsyncSESv2Client


async def main():
    async with AsyncSESv2Client() as se_sv2:
        # Example: call the associate_email_identity_certificate operation
        response = await se_sv2.associate_email_identity_certificate()
        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_sesv2 import AsyncSESv2Client


async def main():
    async with AsyncSESv2Client() as se_sv2:
        # Example: paginate over get_dedicated_ips
        async for item in se_sv2.iter_get_dedicated_ips():
            print(item)

Error Handling

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

from capo_sesv2 import AsyncSESv2Client
from capo_sesv2.error import AlreadyExistsException


async def main():
    async with AsyncSESv2Client() as se_sv2:
        try:
            await se_sv2.associate_email_identity_certificate()
        except AlreadyExistsException 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_sesv2 import AsyncSESv2Client


async def main():
    async with AsyncSESv2Client() as se_sv2:
        # Default: 3 attempts for every operation
        response = await se_sv2.associate_email_identity_certificate()

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

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

Metadata

Release files for capo-sesv2 0.9.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-sesv2 0.9.0
File Size Uploaded Provenance
capo_sesv2-0.9.0.tar.gz 297.9 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-sesv2 0.9.0
File Interpreter ABI Platform
capo_sesv2-0.9.0-py3-none-any.whl Python 3 none any Details

Total release size: 1.1 MB

Release files / capo_sesv2-0.9.0.tar.gz

Download URL capo_sesv2-0.9.0.tar.gz
Size 297.9 kB
Tags Source
SHA-256 checksum
How to use checksums
b02fb23c39689d5558903079af4e3432ee7c8f942b8b5e14bc4526783b4c49bf
BLAKE2b-256 checksum
How to use checksums
2c10ebcb09679e4e9f8bbd3c7b49f94e58e2d55fd0c407e22205a5be6e77e828
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_sesv2-0.9.0-py3-none-any.whl

Download URL capo_sesv2-0.9.0-py3-none-any.whl
Size 772.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ea0aac4ec57399527955e2457df1285374416691a2355c07a0e6becf63046fd8
BLAKE2b-256 checksum
How to use checksums
4c29d26f432152f77f8617752dfe6f28003478c0066b0c8036ef9b320f55a447
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-sesv2 0.9.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