Getting Started
Installation
pip install capo-ebs
Usage
from capo_ebs import AsyncEBSClient
async def main():
async with AsyncEBSClient() as ebs:
# Example: call the complete_snapshot operation
response = await ebs.complete_snapshot()
print(response["status"])
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_ebs import AsyncEBSClient
async def main():
async with AsyncEBSClient() as ebs:
# Example: paginate over list_changed_blocks
async for item in ebs.iter_list_changed_blocks():
print(item)
Streaming Request
Some operations accept a streaming request body. Pass an async iterator of bytes chunks, or the whole body as bytes, for the streaming parameter.
A plain iterator can be sent only once, so if a request fails after its body was transmitted the operation is not retried. To get retries for streamed uploads, pass a Body instead: it wraps a source that can be reopened, and every attempt streams a fresh copy. Body.from_path (sync client) and Body.async_from_path (async client, needs anyio) stream a file from disk; Body(opener) takes any context manager that yields a (stream, length) pair.
from capo_ebs import AsyncEBSClient, Body
async def main():
async with AsyncEBSClient() as ebs:
# Example: call put_snapshot_block with a streaming request body
async def chunks():
yield b'Hello, World!'
response = await ebs.put_snapshot_block(block_data=chunks())
print(response)
# Or pass the whole body as bytes
response = await ebs.put_snapshot_block(block_data=b'Hello, World!')
print(response)
# Or stream a file with Body: the file is reopened on every retry
# and Content-Length is taken from its size, so no content_length needed
response = await ebs.put_snapshot_block(block_data=Body.async_from_path("hello.txt"))
print(response)
Streaming Response
Some operations return a streaming response body. Use the operation as an async context manager and iterate over the response field to read chunks.
from capo_ebs import AsyncEBSClient
async def main():
async with AsyncEBSClient() as ebs:
# Example: call get_snapshot_block and read the streaming response
async with ebs.get_snapshot_block() as response:
async for chunk in response["block_data"]:
print(chunk)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_ebs import AsyncEBSClient
from capo_ebs.error import AccessDeniedException
async def main():
async with AsyncEBSClient() as ebs:
try:
await ebs.complete_snapshot()
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_ebs import AsyncEBSClient
async def main():
async with AsyncEBSClient() as ebs:
# Default: 3 attempts for every operation
response = await ebs.complete_snapshot()
# Override per operation
response = await ebs.complete_snapshot(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await ebs.complete_snapshot(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-ebs 0.2.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_ebs-0.2.0.tar.gz | 73.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_ebs-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 178.2 kB
Release files / capo_ebs-0.2.0.tar.gz
| Download URL | capo_ebs-0.2.0.tar.gz |
|---|---|
| Size | 73.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b94b21375a3aeff814aa1cab3c6197f9329d67d8cce84a15af86b08ab2e3f7a
|
|
BLAKE2b-256 checksum How to use checksums |
183a216c7919a98d72f34fe4d6b2a6d3f72110da75d2b97e5278875fe515157c
|
| 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_ebs-0.2.0-py3-none-any.whl
| Download URL | capo_ebs-0.2.0-py3-none-any.whl |
|---|---|
| Size | 104.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b4de82bac3e29b0cf89796c847c482342afbe1f1a6fd9501ab9373d2bb644244
|
|
BLAKE2b-256 checksum How to use checksums |
ed36bc9b3cf13dc347610cf46068f033b8788ebaa029bc3db0a8ac9dd1602738
|
| 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-ebs 0.2.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.