mypy-boto3-cloudfront-keyvaluestore Type Annotations

Warnings

• breaking Python 3.8 support has been removed since `mypy-boto3-builder` version 8.12.0. If you are using `mypy-boto3-cloudfront-keyvaluestore` version 1.42.3 or newer, your project must use Python 3.9 or higher.
  Fix: Upgrade your Python environment to 3.9 or later. If unable to upgrade Python, pin `mypy-boto3-cloudfront-keyvaluestore` to an older version (e.g., <1.42.3) that was built with `mypy-boto3-builder` versions supporting Python 3.8.
• gotcha The version of `mypy-boto3-cloudfront-keyvaluestore` must closely match your installed `boto3` version. Mismatched versions can lead to incorrect or missing type hints, causing MyPy errors or silently allowing runtime issues.
  Fix: Always install `mypy-boto3-cloudfront-keyvaluestore` with the same major and minor version as your `boto3` package. For example, if you use `boto3==1.42.3`, install `mypy-boto3-cloudfront-keyvaluestore==1.42.3`.
• breaking Starting with `mypy-boto3-builder` version 8.9.0, some TypeDef names were changed to be shorter (e.g., `CreateDistributionRequestRequestTypeDef` became `CreateDistributionRequestTypeDef`) and conflicting `Extra` postfixes were reordered. While this specific service might not be directly affected, be aware of potential TypeDef renaming if migrating existing code using `mypy-boto3`.
  Fix: Review your code for direct imports or references to `TypeDef` classes from `mypy-boto3` packages after upgrading. Update class names according to the new conventions, often found in the generated `type_defs.pyi` files or release notes.
• gotcha Beginning with `mypy-boto3-builder` version 8.12.0, all generated packages migrated to PEP 561. This change is generally beneficial but might require ensuring your build system or `mypy` configuration correctly discovers the stubs, especially in complex project setups or when using `pip install -e .` (editable installs).
  Fix: For editable installs, ensure `pyproject.toml` or `setup.py` correctly declares the package as `py.typed`. If `mypy` has trouble finding stubs, verify your `mypy` configuration (`mypy.ini`) and environment variables (`MYPYPATH`).

Install

• pip install mypy-boto3-cloudfront-keyvaluestore Install package

Imports

• CloudFrontKeyValueStoreClient

  from mypy_boto3_cloudfront_keyvaluestore.client import CloudFrontKeyValueStoreClient

• Client

  from mypy_boto3_cloudfront_keyvaluestore import Client as CloudFrontKeyValueStoreClient

  A top-level alias for the client type is often provided for convenience.

Quickstart

Demonstrates how to import and use the `CloudFrontKeyValueStoreClient` type hint to annotate a boto3 client, enabling static type checking for your CloudFrontKeyValueStore operations.

import boto3
from mypy_boto3_cloudfront_keyvaluestore.client import CloudFrontKeyValueStoreClient

def get_key_value_client() -> CloudFrontKeyValueStoreClient:
    """Gets a typed CloudFront KeyValueStore client."""
    client: CloudFrontKeyValueStoreClient = boto3.client("cloudfront-keyvaluestore")
    return client

# Example usage (requires an AWS setup, e.g., via ~/.aws/credentials)
if __name__ == "__main__":
    try:
        cfkvs_client = get_key_value_client()
        print(f"Successfully created CloudFront KeyValueStore client: {cfkvs_client.meta.region_name}")
        # You can now use cfkvs_client with type hints
        # For example, to list key value stores (if you have any):
        # response = cfkvs_client.list_key_value_stores()
        # print(response)
    except Exception as e:
        print(f"Error creating client: {e}")