Skip to main content

Getting Started

Installation

pip install capo-applicationcostprofiler

Usage

from capo_applicationcostprofiler import AsyncApplicationCostProfilerClient


async def main():
    async with AsyncApplicationCostProfilerClient() as application_cost_profiler:
        # Example: call the delete_report_definition operation
        response = await application_cost_profiler.delete_report_definition()
        print(response["report_id"])

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_applicationcostprofiler import AsyncApplicationCostProfilerClient


async def main():
    async with AsyncApplicationCostProfilerClient() as application_cost_profiler:
        # Example: paginate over list_report_definitions
        async for item in application_cost_profiler.iter_list_report_definitions():
            print(item)

Error Handling

The SDK raises exceptions for errors returned by the API. Catch them to handle failures gracefully.

from capo_applicationcostprofiler import AsyncApplicationCostProfilerClient
from capo_applicationcostprofiler.error import AccessDeniedException


async def main():
    async with AsyncApplicationCostProfilerClient() as application_cost_profiler:
        try:
            await application_cost_profiler.delete_report_definition()
        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_applicationcostprofiler import AsyncApplicationCostProfilerClient


async def main():
    async with AsyncApplicationCostProfilerClient() as application_cost_profiler:
        # Default: 3 attempts for every operation
        response = await application_cost_profiler.delete_report_definition()

        # Override per operation
        response = await application_cost_profiler.delete_report_definition(config_overrides={"retry_max_attempts": 5})

        # Disable retries for this call
        response = await application_cost_profiler.delete_report_definition(config_overrides={"retry_max_attempts": 1})

Metadata

Release files for capo-applicationcostprofiler 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for capo-applicationcostprofiler 0.2.0
File Size Uploaded Provenance
capo_applicationcostprofiler-0.2.0.tar.gz 56.0 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-applicationcostprofiler 0.2.0
File Interpreter ABI Platform
capo_applicationcostprofiler-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 140.8 kB

Release files / capo_applicationcostprofiler-0.2.0.tar.gz

Download URL capo_applicationcostprofiler-0.2.0.tar.gz
Size 56.0 kB
Tags Source
SHA-256 checksum
How to use checksums
da2608bc3622220bde000a0cee15fb90ea4d1aa8e933dbe450a7b597bfe6359d
BLAKE2b-256 checksum
How to use checksums
983b988dbe718cb4e14f275fb5c1c2beedbe31d1188425af5f5ddab6e780615d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","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_applicationcostprofiler-0.2.0-py3-none-any.whl

Download URL capo_applicationcostprofiler-0.2.0-py3-none-any.whl
Size 84.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7123c470231adb51e8110ca4cac7e8663abe9242b5699ea9872dd335d0477f8e
BLAKE2b-256 checksum
How to use checksums
c4ad2845f55147b43a73b582178eb5e466912d24b7c113450e97c276ce0fe40d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","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-applicationcostprofiler 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page