Getting Started
Installation
pip install capo-m2
Usage
from capo_m2 import Asyncm2Client
async def main():
async with Asyncm2Client() as m2:
# Example: call the get_signed_bluinsights_url operation
response = await m2.get_signed_bluinsights_url()
print(response["signed_bi_url"])
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_m2 import Asyncm2Client
async def main():
async with Asyncm2Client() as m2:
# Example: paginate over list_engine_versions
async for item in m2.iter_list_engine_versions():
print(item)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_m2 import Asyncm2Client
from capo_m2.error import AccessDeniedException
async def main():
async with Asyncm2Client() as m2:
try:
await m2.get_signed_bluinsights_url()
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_m2 import Asyncm2Client
async def main():
async with Asyncm2Client() as m2:
# Default: 3 attempts for every operation
response = await m2.get_signed_bluinsights_url()
# Override per operation
response = await m2.get_signed_bluinsights_url(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await m2.get_signed_bluinsights_url(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-m2 0.7.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_m2-0.7.0.tar.gz | 139.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_m2-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 435.5 kB
Release files / capo_m2-0.7.0.tar.gz
| Download URL | capo_m2-0.7.0.tar.gz |
|---|---|
| Size | 139.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c87f28ffa1d0af0dfdc2bcf425bd87209b7789ed8329280c4db21fe55701fbbc
|
|
BLAKE2b-256 checksum How to use checksums |
9486d021000926c2458d56ce61f3594ff395e06d0c07671e2d4ad6821ba68062
|
| 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_m2-0.7.0-py3-none-any.whl
| Download URL | capo_m2-0.7.0-py3-none-any.whl |
|---|---|
| Size | 295.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c70cc3775d89eb69c41c1ed0c56608a0a1961f333f0565a720f89e53f1d6d1be
|
|
BLAKE2b-256 checksum How to use checksums |
185b54328e8e8843b86a0ffec8e0dad0211f61302cbaac506f98b4c171df4ef0
|
| 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-m2 0.7.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.