capo-b2bi: typed, async Python SDK for AWS B2Bi
capo-b2bi is a typed Python SDK for AWS B2Bi. It has an async client, Asyncb2biClient, for asyncio and trio, and a sync client, b2biClient, 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/b2bi/
Installation
pip install capo-b2bi
Usage
from capo_b2bi import Asyncb2biClient
async def main():
async with Asyncb2biClient() as b2bi:
# Example: call the create_starter_mapping_template operation
response = await b2bi.create_starter_mapping_template()
print(response["mapping_template"])
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_b2bi import Asyncb2biClient
async def main():
async with Asyncb2biClient() as b2bi:
# Example: paginate over list_capabilities
async for item in b2bi.iter_list_capabilities():
print(item)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_b2bi import Asyncb2biClient
from capo_b2bi.error import AccessDeniedException
async def main():
async with Asyncb2biClient() as b2bi:
try:
await b2bi.create_starter_mapping_template()
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_b2bi import Asyncb2biClient
async def main():
async with Asyncb2biClient() as b2bi:
# Default: 3 attempts for every operation
response = await b2bi.create_starter_mapping_template()
# Override per operation
response = await b2bi.create_starter_mapping_template(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await b2bi.create_starter_mapping_template(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-b2bi 0.11.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_b2bi-0.11.0.tar.gz | 142.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_b2bi-0.11.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 426.4 kB
Release files / capo_b2bi-0.11.0.tar.gz
| Download URL | capo_b2bi-0.11.0.tar.gz |
|---|---|
| Size | 142.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2982e980fe9f4f8717cafd56e25417055bbaef4540e5a68258a0aa91938e9571
|
|
BLAKE2b-256 checksum How to use checksums |
061d17ebfe35a7853f25d1c32cee3b4dce74f1519ee6305d0fa14fe3148ecd41
|
| 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_b2bi-0.11.0-py3-none-any.whl
| Download URL | capo_b2bi-0.11.0-py3-none-any.whl |
|---|---|
| Size | 284.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b3c2640ec876d5bffd8f7d66e09ed1f339325ce90fc16d5e1918f0aa889b1b4c
|
|
BLAKE2b-256 checksum How to use checksums |
c362363b438008e884722b55187829fd56539a8918fdbe8cbc2d9d0007271172
|
| 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-b2bi 0.11.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.