Skip to main content

capo-forecast: typed, async Python SDK for AWS Forecast

capo-forecast is a typed Python SDK for AWS Forecast. It has an async client, AsyncforecastClient, for asyncio and trio, and a sync client, forecastClient, 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/forecast/

Installation

pip install capo-forecast

Usage

from capo_forecast import AsyncforecastClient


async def main():
    async with AsyncforecastClient() as forecast:
        # Example: call the create_auto_predictor operation
        response = await forecast.create_auto_predictor()
        print(response["predictor_arn"])

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_forecast import AsyncforecastClient


async def main():
    async with AsyncforecastClient() as forecast:
        # Example: paginate over list_dataset_groups
        async for item in forecast.iter_list_dataset_groups():
            print(item)

Error Handling

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

from capo_forecast import AsyncforecastClient
from capo_forecast.error import InvalidInputException


async def main():
    async with AsyncforecastClient() as forecast:
        try:
            await forecast.create_auto_predictor()
        except InvalidInputException 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_forecast import AsyncforecastClient


async def main():
    async with AsyncforecastClient() as forecast:
        # Default: 3 attempts for every operation
        response = await forecast.create_auto_predictor()

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

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

Metadata

Release files for capo-forecast 0.10.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-forecast 0.10.0
File Size Uploaded Provenance
capo_forecast-0.10.0.tar.gz 191.0 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for capo-forecast 0.10.0
File Interpreter ABI Platform
capo_forecast-0.10.0-py3-none-any.whl Python 3 none any Details

Total release size: 642.6 kB

Release files / capo_forecast-0.10.0.tar.gz

Download URL capo_forecast-0.10.0.tar.gz
Size 191.0 kB
Tags Source
SHA-256 checksum
How to use checksums
50b62340f48d6e69cc601d3b7098c147797722a3625ee5cc03e11862d8eeecae
BLAKE2b-256 checksum
How to use checksums
b74d2dd168894ce134dbd7d5caf24f6ee53895b6eca6cc9cae9cbf6b37bd0b52
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","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_forecast-0.10.0-py3-none-any.whl

Download URL capo_forecast-0.10.0-py3-none-any.whl
Size 451.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
633454a2b69d12c5e39ddae560303ed2ec73dd8c5d45c7ddb003ad29b6e8b7ac
BLAKE2b-256 checksum
How to use checksums
413afd20cad55042d5fadeb61a1948c5c4397e1a124ba1f9b9c5df0bc30ca5fb
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","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-forecast 0.10.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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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