Getting Started
Installation
pip install capo-scheduler
Usage
from capo_scheduler import AsyncSchedulerClient
async def main():
async with AsyncSchedulerClient() as scheduler:
# Example: call the list_tags_for_resource operation
response = await scheduler.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_scheduler import AsyncSchedulerClient
async def main():
async with AsyncSchedulerClient() as scheduler:
# Example: paginate over list_schedules
async for item in scheduler.iter_list_schedules():
print(item)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_scheduler import AsyncSchedulerClient
from capo_scheduler.error import InternalServerException
async def main():
async with AsyncSchedulerClient() as scheduler:
try:
await scheduler.list_tags_for_resource()
except InternalServerException 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_scheduler import AsyncSchedulerClient
async def main():
async with AsyncSchedulerClient() as scheduler:
# Default: 3 attempts for every operation
response = await scheduler.list_tags_for_resource()
# Override per operation
response = await scheduler.list_tags_for_resource(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await scheduler.list_tags_for_resource(config_overrides={"retry_max_attempts": 1})
1 maintainer
Metadata
1 maintainer
Release files for capo-scheduler 0.13.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_scheduler-0.13.0.tar.gz | 90.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_scheduler-0.13.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 247.4 kB
Release files / capo_scheduler-0.13.0.tar.gz
| Download URL | capo_scheduler-0.13.0.tar.gz |
|---|---|
| Size | 90.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ef4b8a6fb06f31cecb1defc1f1b7ecda29e0dcac569d5c1e173a6303e764cad
|
|
BLAKE2b-256 checksum How to use checksums |
062d596bba4762b072db396540d2eab72b4a9d317258c3f5e5c018666c8d368c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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_scheduler-0.13.0-py3-none-any.whl
| Download URL | capo_scheduler-0.13.0-py3-none-any.whl |
|---|---|
| Size | 156.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d67831c38bf41006780c4178f7f68454993e8d2a788a5f5b706c58468c158bac
|
|
BLAKE2b-256 checksum How to use checksums |
6d82a6346c4bac39af9f0eb1e4625750c07a8c3fc91720b8f6cc03b46b2d8fa0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.22 {"installer":{"name":"uv","version":"0.12.22","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-scheduler 0.13.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.
