Skip to main content

capo-pcs: typed, async Python SDK for AWS PCS

capo-pcs is a typed Python SDK for AWS PCS. It has an async client, AsyncPCSClient, for asyncio and trio, and a sync client, PCSClient, 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/pcs/

Installation

pip install capo-pcs

Usage

from capo_pcs import AsyncPCSClient


async def main():
    async with AsyncPCSClient() as pcs:
        # Example: call the list_tags_for_resource operation
        response = await pcs.list_tags_for_resource()
        print(response["tags"])

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_pcs import AsyncPCSClient


async def main():
    async with AsyncPCSClient() as pcs:
        # Example: paginate over list_clusters
        async for item in pcs.iter_list_clusters():
            print(item)

Error Handling

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

from capo_pcs import AsyncPCSClient
from capo_pcs.error import ResourceNotFoundException


async def main():
    async with AsyncPCSClient() as pcs:
        try:
            await pcs.list_tags_for_resource()
        except ResourceNotFoundException 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_pcs import AsyncPCSClient


async def main():
    async with AsyncPCSClient() as pcs:
        # Default: 3 attempts for every operation
        response = await pcs.list_tags_for_resource()

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

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

Metadata

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

Built distribution (wheel)

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

Total release size: 339.4 kB

Release files / capo_pcs-0.9.0.tar.gz

Download URL capo_pcs-0.9.0.tar.gz
Size 117.7 kB
Tags Source
SHA-256 checksum
How to use checksums
310d2ac5c26df6d5cb622e67e0759823ca7b624142b499ee0cce13629415ad79
BLAKE2b-256 checksum
How to use checksums
b4d5a4f95f0b580a5e56c47a7500fc83a054c7ff306d10e44b970721c88e0896
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_pcs-0.9.0-py3-none-any.whl

Download URL capo_pcs-0.9.0-py3-none-any.whl
Size 221.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
68b67383c5170e1635c68f80778228eca1fbb7109c106e6f1d342ca3f617e8c3
BLAKE2b-256 checksum
How to use checksums
863a77a65f322e4d9fd79cda09c3f6439a9a6ade3acff900aac653da04740984
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-pcs 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