Getting Started
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.12.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_ecr-0.12.0.tar.gz | 188.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_ecr-0.12.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 669.1 kB
Release files / capo_ecr-0.12.0.tar.gz
| Download URL | capo_ecr-0.12.0.tar.gz |
|---|---|
| Size | 188.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
366dacb9a6f0190802c53b0741099ce78e0832b5ece903ef00f6d8d90437f2ff
|
|
BLAKE2b-256 checksum How to use checksums |
0a391a9353efd151dfcd907675a385651b9ddda6ce30341f07198cc66ccbcfe4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","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.12.0-py3-none-any.whl
| Download URL | capo_ecr-0.12.0-py3-none-any.whl |
|---|---|
| Size | 481.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ffb01acfc46fd03dccfa36c0112a3fd652aa0c1ad654467ee855672b0121a0b8
|
|
BLAKE2b-256 checksum How to use checksums |
0886078a801549262db7e21a04d84badab2ee64b77ad4f9b79792ee4ed72ae4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","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.12.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.