Getting Started
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"])
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.1.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_pcs-0.1.0.tar.gz | 82.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_pcs-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 265.7 kB
Release files / capo_pcs-0.1.0.tar.gz
| Download URL | capo_pcs-0.1.0.tar.gz |
|---|---|
| Size | 82.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f324904f24c69e136382bd1e7ddd49017933a8abe2fb51d52b7e7c21805894e3
|
|
BLAKE2b-256 checksum How to use checksums |
7b2e73cada940b0e5556551746951160fc7b702b7ac2039e8574342c71bba193
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.19 {"installer":{"name":"uv","version":"0.12.19","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.1.0-py3-none-any.whl
| Download URL | capo_pcs-0.1.0-py3-none-any.whl |
|---|---|
| Size | 183.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d43599e54e5102b39d0bd499bb5bdf4dfdc197b5fe5fbaed2df7f8887b8fdc8c
|
|
BLAKE2b-256 checksum How to use checksums |
b869c1aaf41941e51c5d8d31dec29a449843652b7021cd321e216358be9b2c63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.19 {"installer":{"name":"uv","version":"0.12.19","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.1.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.