Skip to main content

capo-ecr: typed, async Python SDK for AWS ECR

capo-ecr is a typed Python SDK for AWS ECR. It has an async client, AsyncECRClient, for asyncio and trio, and a sync client, ECRClient, 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/ecr/

Installation

pip install capo-ecr

Usage

from capo_ecr import AsyncECRClient


async def main():
    async with AsyncECRClient() as ecr:
        # Example: call the batch_check_layer_availability operation
        response = await ecr.batch_check_layer_availability()
        print(response["layers"])

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_ecr import AsyncECRClient


async def main():
    async with AsyncECRClient() as ecr:
        # Example: paginate over describe_images
        async for item in ecr.iter_describe_images():
            print(item)

Error Handling

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

from capo_ecr import AsyncECRClient
from capo_ecr.error import InvalidParameterException


async def main():
    async with AsyncECRClient() as ecr:
        try:
            await ecr.batch_check_layer_availability()
        except InvalidParameterException 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_ecr import AsyncECRClient


async def main():
    async with AsyncECRClient() as ecr:
        # Default: 3 attempts for every operation
        response = await ecr.batch_check_layer_availability()

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

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

Metadata

Release files for capo-ecr 0.17.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-ecr 0.17.0
File Size Uploaded Provenance
capo_ecr-0.17.0.tar.gz 193.4 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-ecr 0.17.0
File Interpreter ABI Platform
capo_ecr-0.17.0-py3-none-any.whl Python 3 none any Details

Total release size: 681.0 kB

Release files / capo_ecr-0.17.0.tar.gz

Download URL capo_ecr-0.17.0.tar.gz
Size 193.4 kB
Tags Source
SHA-256 checksum
How to use checksums
1f1182872f02a239e2a0e566f4fd5e63e1de6acd178935ccdc4ffa1c1cd4fab1
BLAKE2b-256 checksum
How to use checksums
71436542483fd3f1949e292b04a2dd4818ada587847262dc9537035a368ddf00
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_ecr-0.17.0-py3-none-any.whl

Download URL capo_ecr-0.17.0-py3-none-any.whl
Size 487.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c08a98e7d99edc9c7090f5809890bf4ab8c971ef7c005e7ba3989e8f58ad5d20
BLAKE2b-256 checksum
How to use checksums
dbf8523612ca6136b94f6cb75492a536be3bf3b66cd3fcc9640470afc130dc54
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-ecr 0.17.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