Registry /
type-stubs / mypy-boto3-billingconductor
Install & Compatibility
Where this runs
tested against v1.43.7 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
muslpy 3.10–3.95 runs
installs and imports cleanly · install 0.0s · import 0.622s · 52.1MB
glibcpy 3.10–3.95 runs
installs and imports cleanly · install 3.8s · import 0.572s · 53MB
50MB installed
● package 50MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
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`.
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.")
Debug
Known issues
breakingPython 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`.fixUpgrade 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`).
affects: mypy-boto3-billingconductor versions generated with `mypy-boto3-builder >= 8.12.0`
breakingPackages 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.fixEnsure your development environment and type checkers are updated to support PEP 561. Most modern setups (e.g., mypy, pyright, Pylance) handle this automatically.
affects: mypy-boto3-billingconductor versions generated with `mypy-boto3-builder >= 8.12.0`
deprecatedThe 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.fixMigrate your `pip install` commands from `mypy-boto3` to `types-boto3` (for all services) or directly `mypy-boto3-billingconductor` for specific service stubs.
affects: All versions of legacy `mypy-boto3` (not `mypy-boto3-builder`)
gotchaThis 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.fixAlways install `boto3` alongside `mypy-boto3-billingconductor`: `pip install boto3 mypy-boto3-billingconductor`.
affects: All versions
gotchaFor 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.fixAlways add explicit type hints to your `boto3` client and resource objects using the imported types from `mypy_boto3_billingconductor`.
affects: All versions
gotchaWhen 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`.fixAs 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.
affects: All versions when using `pylint` with `TYPE_CHECKING` guards
Upgrade
Version history
1.43.7latest on PyPI · released May 13, 2026
Audit
Dependencies
boto3requiredProvides the runtime functionality; mypy-boto3-billingconductor only supplies type stubs for it.