capo-odb: typed, async Python SDK for AWS ODB
capo-odb is a typed Python SDK for AWS ODB. It has an async client, AsyncodbClient, for asyncio and trio, and a sync client, odbClient, 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/odb/
Installation
pip install capo-odb
Usage
from capo_odb import AsyncodbClient
async def main():
async with AsyncodbClient() as odb:
# Example: call the accept_marketplace_registration operation
response = await odb.accept_marketplace_registration()
print(response)
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_odb import AsyncodbClient
async def main():
async with AsyncodbClient() as odb:
# Example: paginate over list_autonomous_database_character_sets
async for item in odb.iter_list_autonomous_database_character_sets():
print(item)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_odb import AsyncodbClient
from capo_odb.error import AccessDeniedException
async def main():
async with AsyncodbClient() as odb:
try:
await odb.accept_marketplace_registration()
except AccessDeniedException 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_odb import AsyncodbClient
async def main():
async with AsyncodbClient() as odb:
# Default: 3 attempts for every operation
response = await odb.accept_marketplace_registration()
# Override per operation
response = await odb.accept_marketplace_registration(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await odb.accept_marketplace_registration(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-odb 0.9.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_odb-0.9.0.tar.gz | 278.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_odb-0.9.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 918.9 kB
Release files / capo_odb-0.9.0.tar.gz
| Download URL | capo_odb-0.9.0.tar.gz |
|---|---|
| Size | 278.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ab246800b7b7e23161f2c074dc57fe77d39cbfe054f9a6f8ade0eeac24b09d82
|
|
BLAKE2b-256 checksum How to use checksums |
389cade046f4205b9b30e5ca098f196b46e94d384839adcf8bed2dd02fbec8a9
|
| 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_odb-0.9.0-py3-none-any.whl
| Download URL | capo_odb-0.9.0-py3-none-any.whl |
|---|---|
| Size | 640.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b1f38add55e52a13be4f31aff7332f4da54d73483e0600c4adccd2e2e2ef82c2
|
|
BLAKE2b-256 checksum How to use checksums |
665d9b5f57213a505b3dd00cb8a350ab070c8159a531ab9d7e1ef4a4436d413e
|
| 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-odb 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.