Skip to main content

capo-repostspace: typed, async Python SDK for AWS Repostspace

capo-repostspace is a typed Python SDK for AWS Repostspace. It has an async client, AsyncrepostspaceClient, for asyncio and trio, and a sync client, repostspaceClient, 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/repostspace/

Installation

pip install capo-repostspace

Usage

from capo_repostspace import AsyncrepostspaceClient


async def main():
    async with AsyncrepostspaceClient() as repostspace:
        # Example: call the batch_add_channel_role_to_accessors operation
        response = await repostspace.batch_add_channel_role_to_accessors()
        print(response["added_accessor_ids"])

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_repostspace import AsyncrepostspaceClient


async def main():
    async with AsyncrepostspaceClient() as repostspace:
        # Example: paginate over list_channels
        async for item in repostspace.iter_list_channels():
            print(item)

Error Handling

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

from capo_repostspace import AsyncrepostspaceClient
from capo_repostspace.error import AccessDeniedException


async def main():
    async with AsyncrepostspaceClient() as repostspace:
        try:
            await repostspace.batch_add_channel_role_to_accessors()
        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_repostspace import AsyncrepostspaceClient


async def main():
    async with AsyncrepostspaceClient() as repostspace:
        # Default: 3 attempts for every operation
        response = await repostspace.batch_add_channel_role_to_accessors()

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

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

Metadata

Release files for capo-repostspace 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-repostspace 0.8.0
File Size Uploaded Provenance
capo_repostspace-0.8.0.tar.gz 87.0 kB Without provenance Details

Built distribution (wheel)

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

Total release size: 246.1 kB

Release files / capo_repostspace-0.8.0.tar.gz

Download URL capo_repostspace-0.8.0.tar.gz
Size 87.0 kB
Tags Source
SHA-256 checksum
How to use checksums
247bf79dc9f4790c526845c13ff95aef2be68711ed856781f8cacc120a40131b
BLAKE2b-256 checksum
How to use checksums
b98e57168ed0da6c5dfaeaf76da70f5fc255f8b466f35851b0487c256f67d419
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_repostspace-0.8.0-py3-none-any.whl

Download URL capo_repostspace-0.8.0-py3-none-any.whl
Size 159.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
43bfcbd3719c51ea3bc0e04dc1bef6a1ff3406543ed7a98a83e4be838e78713e
BLAKE2b-256 checksum
How to use checksums
20ec788fc1744374f9e98f70f808b4d38f743a803ce0a245ca9d9e86333ce75e
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-repostspace 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