Skip to main content

capo-signer-data: typed, async Python SDK for AWS Signer Data

capo-signer-data is a typed Python SDK for AWS Signer Data. It has an async client, AsyncSignerDataClient, for asyncio and trio, and a sync client, SignerDataClient, 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/signer-data/

Installation

pip install capo-signer-data

Usage

from capo_signer_data import AsyncSignerDataClient


async def main():
    async with AsyncSignerDataClient() as signer_data:
        # Example: call the get_revocation_status operation
        response = await signer_data.get_revocation_status()
        print(response["revoked_entities"])

Error Handling

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

from capo_signer_data import AsyncSignerDataClient
from capo_signer_data.error import AccessDeniedException


async def main():
    async with AsyncSignerDataClient() as signer_data:
        try:
            await signer_data.get_revocation_status()
        except AccessDeniedException 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_signer_data import AsyncSignerDataClient


async def main():
    async with AsyncSignerDataClient() as signer_data:
        # Default: 3 attempts for every operation
        response = await signer_data.get_revocation_status()

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

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

Metadata

Release files for capo-signer-data 0.8.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-signer-data 0.8.0
File Size Uploaded Provenance
capo_signer_data-0.8.0.tar.gz 56.8 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-signer-data 0.8.0
File Interpreter ABI Platform
capo_signer_data-0.8.0-py3-none-any.whl Python 3 none any Details

Total release size: 120.6 kB

Release files / capo_signer_data-0.8.0.tar.gz

Download URL capo_signer_data-0.8.0.tar.gz
Size 56.8 kB
Tags Source
SHA-256 checksum
How to use checksums
f0f4cba0fd7b2c5263b0ac3679b70771a8dec0d68185cfb6b6a7e069696f7c2a
BLAKE2b-256 checksum
How to use checksums
bfe653244c2cbc72adcd00f6b46227a2e0fda9c822f927a792a076aeb25c7b6f
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_signer_data-0.8.0-py3-none-any.whl

Download URL capo_signer_data-0.8.0-py3-none-any.whl
Size 63.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
893033bb76886a213f3b45d44e190a7a0d359710689fa2ef5484959697e5b297
BLAKE2b-256 checksum
How to use checksums
f725bedf78350b7ce117f804b5d1abeffc2146b76b942ba579f9a3184c730686
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-signer-data 0.8.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