mypy-boto3-billingconductor Type Annotations

Warnings

• breaking Python 3.8 support has been removed for packages generated by `mypy-boto3-builder` version 8.12.0 and newer. This specific `mypy-boto3-billingconductor` version (1.42.7) was generated with `builder 8.12.0`.
  Fix: Upgrade your Python environment to 3.9 or higher. If you must use Python 3.8, you will need to pin to an older `mypy-boto3-billingconductor` version generated with an older builder (e.g., `<1.42.7`).
• breaking Packages generated by `mypy-boto3-builder` (version 8.12.0 onwards) have migrated to PEP 561-compliant distribution. While generally seamless, if you have custom build processes or tools that rely on specific stub discovery mechanisms, you might need to verify compatibility.
  Fix: Ensure your development environment and type checkers are updated to support PEP 561. Most modern setups (e.g., mypy, pyright, Pylance) handle this automatically.
• deprecated The original `mypy-boto3` package is now considered 'legacy'. Users are encouraged to install service-specific packages (like `mypy-boto3-billingconductor`) or the umbrella `types-boto3` or `boto3-stubs` packages for type annotations.
  Fix: Migrate your `pip install` commands from `mypy-boto3` to `types-boto3` (for all services) or directly `mypy-boto3-billingconductor` for specific service stubs.
• gotcha This library only provides type annotations. The actual `boto3` runtime library must be installed separately for your code to execute. Without `boto3` installed, your code will fail at runtime.
  Fix: Always install `boto3` alongside `mypy-boto3-billingconductor`: `pip install boto3 mypy-boto3-billingconductor`.
• gotcha For optimal IDE code completion and faster type checking, especially in older IDEs or specific `mypy` configurations, explicit type annotations (e.g., `client: BillingConductorClient = session.client('billingconductor')`) are recommended rather than relying solely on inference.
  Fix: Always add explicit type hints to your `boto3` client and resource objects using the imported types from `mypy_boto3_billingconductor`.
• gotcha When using `if TYPE_CHECKING:` for conditional imports to avoid runtime dependencies, `pylint` may incorrectly report 'undefined variable' errors. This is a known issue with `pylint`.
  Fix: As a workaround, outside the `TYPE_CHECKING` block, assign `object` to the imported types (e.g., `else: BillingConductorClient = object`). Alternatively, configure `pylint` to ignore these specific warnings.

Install

• pip install mypy-boto3-billingconductor boto3 Install with pip

Imports

• BillingConductorClient

  from mypy_boto3_billingconductor.client import BillingConductorClient

  This is the primary way to import the client type for type hinting.
• BillingConductorServiceResource

  from mypy_boto3_billingconductor.service_resource import BillingConductorServiceResource

  Use this for type hinting the service resource.
• CreatePricingRuleResponseTypeDef

  from mypy_boto3_billingconductor.type_defs import CreatePricingRuleResponseTypeDef

  Type definitions for response objects and other complex structures are found in `type_defs`.

Quickstart

This example demonstrates how to set up a `boto3` client for BillingConductor with type annotations provided by `mypy-boto3-billingconductor`. The `TYPE_CHECKING` block ensures that the stub import is only used during type checking, avoiding runtime dependencies. It then attempts to list pricing plans, showcasing basic usage.

import boto3
from typing import TYPE_CHECKING

if TYPE_CHECKING:
    from mypy_boto3_billingconductor.client import BillingConductorClient

session = boto3.Session()
client: BillingConductorClient = session.client("billingconductor")

try:
    # Example: List Pricing Plans (assuming you have some)
    response = client.list_pricing_plans(
        MaxResults=5
    )
    print(f"Pricing Plans: {response.get('PricingPlans')}")
    print("Quickstart executed successfully, type hints are active.")
except Exception as e:
    print(f"An error occurred: {e}")
    print("This is expected if AWS credentials are not configured or no pricing plans exist.")