capo-signer: typed, async Python SDK for AWS Signer
capo-signer is a typed Python SDK for AWS Signer. It has an async client, AsyncsignerClient, for asyncio and trio, and a sync client, signerClient, 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/
Installation
pip install capo-signer
Usage
from capo_signer import AsyncsignerClient
async def main():
async with AsyncsignerClient() as signer:
# Example: call the add_profile_permission operation
response = await signer.add_profile_permission()
print(response["revision_id"])
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_signer import AsyncsignerClient
async def main():
async with AsyncsignerClient() as signer:
# Example: paginate over list_signing_jobs
async for item in signer.iter_list_signing_jobs():
print(item)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_signer import AsyncsignerClient
from capo_signer.error import AccessDeniedException
async def main():
async with AsyncsignerClient() as signer:
try:
await signer.add_profile_permission()
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 import AsyncsignerClient
async def main():
async with AsyncsignerClient() as signer:
# Default: 3 attempts for every operation
response = await signer.add_profile_permission()
# Override per operation
response = await signer.add_profile_permission(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await signer.add_profile_permission(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-signer 0.9.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| capo_signer-0.9.0.tar.gz | 99.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_signer-0.9.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 278.7 kB
Release files / capo_signer-0.9.0.tar.gz
| Download URL | capo_signer-0.9.0.tar.gz |
|---|---|
| Size | 99.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a2532f8a55964bcd5903e7777362dc49b4d3482002bd1c45d150ae94493017b1
|
|
BLAKE2b-256 checksum How to use checksums |
b9a9ef674981c8f6055bd8a953aafe58d68b12e8c83e08ea5676e9b7e3202c75
|
| 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-0.9.0-py3-none-any.whl
| Download URL | capo_signer-0.9.0-py3-none-any.whl |
|---|---|
| Size | 179.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9796b0da2eb5680b24dd5899027cdd16a765e26751e40e9187aad0325147b607
|
|
BLAKE2b-256 checksum How to use checksums |
d84c77a4858ea98c6507d09c3631e521253c0f3d8e03bd0fbfcbfe426e4b8a3f
|
| 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 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.