Skip to main content

Getting Started

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.3.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.3.0
File Size Uploaded Provenance
capo_signer_data-0.3.0.tar.gz 52.3 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 111.4 kB

Release files / capo_signer_data-0.3.0.tar.gz

Download URL capo_signer_data-0.3.0.tar.gz
Size 52.3 kB
Tags Source
SHA-256 checksum
How to use checksums
d3652f03d78f7a9adb7e43351fe444a96501a5486ba3a753298c924eb2120b3e
BLAKE2b-256 checksum
How to use checksums
55b8be0d696323ff068e1197aca457ec738172ac7efe76ffe5049fd32e7e82f0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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.3.0-py3-none-any.whl

Download URL capo_signer_data-0.3.0-py3-none-any.whl
Size 59.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fcbcd6043b3ea31b26be6a71965e9feb354326740f34fb79e8a63c78dc31b0d5
BLAKE2b-256 checksum
How to use checksums
4a5bc54fa8d1dc655efc1860e956f6ce33a0b2ff79431fbb549b5cd98a5ad8ef
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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.3.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