Getting Started
Installation
pip install capo-billingconductor
Usage
from capo_billingconductor import AsyncbillingconductorClient
async def main():
async with AsyncbillingconductorClient() as billingconductor:
# Example: call the get_billing_group_cost_report operation
response = await billingconductor.get_billing_group_cost_report()
print(response["billing_group_cost_report_results"])
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_billingconductor import AsyncbillingconductorClient
async def main():
async with AsyncbillingconductorClient() as billingconductor:
# Example: paginate over get_billing_group_cost_report
async for item in billingconductor.iter_get_billing_group_cost_report():
print(item)
Error Handling
The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.
from capo_billingconductor import AsyncbillingconductorClient
from capo_billingconductor.error import AccessDeniedException
async def main():
async with AsyncbillingconductorClient() as billingconductor:
try:
await billingconductor.get_billing_group_cost_report()
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_billingconductor import AsyncbillingconductorClient
async def main():
async with AsyncbillingconductorClient() as billingconductor:
# Default: 3 attempts for every operation
response = await billingconductor.get_billing_group_cost_report()
# Override per operation
response = await billingconductor.get_billing_group_cost_report(config_overrides={"retry_max_attempts": 5})
# Disable retries for this call
response = await billingconductor.get_billing_group_cost_report(config_overrides={"retry_max_attempts": 1})
Metadata
Release files for capo-billingconductor 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_billingconductor-0.2.0.tar.gz | 125.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| capo_billingconductor-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 426.8 kB
Release files / capo_billingconductor-0.2.0.tar.gz
| Download URL | capo_billingconductor-0.2.0.tar.gz |
|---|---|
| Size | 125.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d82eb9a3e2839c01896387867384c83983ae02a92c1e0ecc5fde0552876d5fae
|
|
BLAKE2b-256 checksum How to use checksums |
886bcd9182ac2d065baac2e140408f6ab65e8bc989f000bf3b7a1c7e93c869f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.16 {"installer":{"name":"uv","version":"0.12.16","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_billingconductor-0.2.0-py3-none-any.whl
| Download URL | capo_billingconductor-0.2.0-py3-none-any.whl |
|---|---|
| Size | 301.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aec592bc55a6ee2ff43b8339e248ece621048634745b232ec5b2fdfb81fc5b68
|
|
BLAKE2b-256 checksum How to use checksums |
ea1a683588735b20028440c545058aa10c6900a68e926740b7d25f029cdf2d40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.16 {"installer":{"name":"uv","version":"0.12.16","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-billingconductor 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.