mypy-boto3-mediapackage-vod

Warnings

• breaking Support for Python 3.8 was removed in `mypy-boto3-builder` version 8.12.0, affecting all generated `mypy-boto3` stub packages, including `mypy-boto3-mediapackage-vod`. Projects using Python 3.8 will no longer receive type hints or updates from this version onwards.
  Fix: Upgrade your Python environment to version 3.9 or newer. The `requires_python` metadata explicitly states `>=3.9`.
• breaking The `mypy-boto3-builder` (which generates this package) migrated to PEP 561 compliant packages in version 8.12.0. This change might affect how some build systems or older static analysis tools interpret the stub distribution.
  Fix: Ensure your `mypy` and build environment are up-to-date and correctly configured to recognize PEP 561 stub-only packages. Most modern Python tooling should handle this automatically.
• gotcha This package provides only type annotations; it does NOT install or include `boto3` itself. For your application to run, `boto3` must be installed separately in your environment.
  Fix: Always ensure you have `pip install boto3` in your project's dependencies alongside `mypy-boto3-mediapackage-vod`.
• breaking Breaking changes were introduced in `mypy-boto3-builder` 8.9.0 regarding `TypedDict` naming conventions. Specifically, method argument `TypeDef`s now use shorter names (e.g., `CreateDistributionRequestRequestTypeDef` -> `CreateDistributionRequestTypeDef`), and conflicting `TypeDef` `Extra` postfixes were moved to the end (e.g., `CreateDistributionExtraRequestTypeDef` -> `CreateDistributionRequestExtraTypeDef`).
  Fix: If your code explicitly imports or references generated `TypedDict` names, you may need to update these references to match the new naming conventions.
• gotcha While many IDEs and `mypy` can infer types, explicitly annotating `boto3.client` and `boto3.resource` calls with the imported client/resource types from `mypy_boto3_servicename` can improve accuracy, especially in IDEs like VSCode or when using 'lite' stub versions.
  Fix: Add explicit type hints to your `boto3` client/resource instantiations, e.g., `client: MediaPackageVodClient = boto3.client('mediapackage-vod')`.

Install

• pip install mypy-boto3-mediapackage-vod Install package

Imports

• MediaPackageVodClient

  from mypy_boto3_mediapackage_vod.client import MediaPackageVodClient

  Importing directly from `boto3.client` will not provide type hints for the specific service client. Ensure you import the typed client from the `mypy_boto3_mediapackage_vod.client` submodule.
• MediaPackageVodServiceName

  from mypy_boto3_mediapackage_vod.literals import MediaPackageVodServiceName

  Used for Literal type hints in overloaded functions for `boto3.client`.

Quickstart

This quickstart demonstrates how to initialize a `boto3` MediaPackageVod client with type hints provided by `mypy-boto3-mediapackage-vod`. The `TYPE_CHECKING` block ensures that type imports are only active during static analysis, preventing runtime dependencies. The example then calls `list_assets` and uses the typed response.

import boto3
from typing import TYPE_CHECKING

if TYPE_CHECKING:
    from mypy_boto3_mediapackage_vod.client import MediaPackageVodClient
    from mypy_boto3_mediapackage_vod.type_defs import ListAssetsResponseTypeDef

def list_vod_assets() -> ListAssetsResponseTypeDef:
    # mypy-boto3-mediapackage-vod provides type hints for the client
    client: MediaPackageVodClient = boto3.client("mediapackage-vod")
    response = client.list_assets()
    return response

if __name__ == "__main__":
    # Example usage (requires AWS credentials configured)
    try:
        assets = list_vod_assets()
        print(f"Found {len(assets.get('Assets', []))} MediaPackage VOD assets.")
    except Exception as e:
        print(f"Error listing assets: {e}")