Skip to main content

capo-wickr: typed, async Python SDK for AWS Wickr

capo-wickr is a typed Python SDK for AWS Wickr. It has an async client, AsyncWickrClient, for asyncio and trio, and a sync client, WickrClient, 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/wickr/

Installation

pip install capo-wickr

Usage

from capo_wickr import AsyncWickrClient


async def main():
    async with AsyncWickrClient() as wickr:
        # Example: call the batch_create_user operation
        response = await wickr.batch_create_user()
        print(response["message"])

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_wickr import AsyncWickrClient


async def main():
    async with AsyncWickrClient() as wickr:
        # Example: paginate over list_blocked_guest_users
        async for item in wickr.iter_list_blocked_guest_users():
            print(item)

Error Handling

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

from capo_wickr import AsyncWickrClient
from capo_wickr.error import BadRequestError


async def main():
    async with AsyncWickrClient() as wickr:
        try:
            await wickr.batch_create_user()
        except BadRequestError 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_wickr import AsyncWickrClient


async def main():
    async with AsyncWickrClient() as wickr:
        # Default: 3 attempts for every operation
        response = await wickr.batch_create_user()

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

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

Metadata

Release files for capo-wickr 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-wickr 0.9.0
File Size Uploaded Provenance
capo_wickr-0.9.0.tar.gz 138.2 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 440.1 kB

Release files / capo_wickr-0.9.0.tar.gz

Download URL capo_wickr-0.9.0.tar.gz
Size 138.2 kB
Tags Source
SHA-256 checksum
How to use checksums
04f28ffed11e7d70ab7d7957a03eee883c44ebfd0d466b3644a433eb7952c2a8
BLAKE2b-256 checksum
How to use checksums
d05f11a4047306bce1d2a690a3f30c8072b44eefbe454877ee5db0a6a4e309c7
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_wickr-0.9.0-py3-none-any.whl

Download URL capo_wickr-0.9.0-py3-none-any.whl
Size 302.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
93e8aae6a21ea10324205c9fd7055ef0cd791779eb18312620ca8ceb052a1af9
BLAKE2b-256 checksum
How to use checksums
d44d20f1ad3439b6df6b6c118c92df2299c2aa80b1ea57fda787d7e9cee5c557
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-wickr 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