Type Annotations for Boto3 Chime SDK Meetings

Warnings

• breaking Python 3.8 support was removed for all generated packages, including `mypy-boto3-chime-sdk-meetings`, with `mypy-boto3-builder` version 8.12.0. Users on Python 3.8 or older must upgrade their Python version.
  Fix: Upgrade your Python environment to 3.9 or newer.
• breaking Starting with `mypy-boto3-builder` 8.9.0, TypeDef names for packed method arguments and conflicting TypeDefs were changed to shorter or re-ordered variants (e.g., `CreateDistributionRequestRequestTypeDef` -> `CreateDistributionRequestTypeDef`). This may require updates to existing type hint usage.
  Fix: Review your code for TypeDef imports and adjust names according to the updated patterns, typically shortening redundant names or moving `Extra` postfixes.
• breaking As of `mypy-boto3-builder` 8.12.0, all packages migrated to PEP 561, making them stub-only packages. While this is an improvement for type checker resolution, ensure your `mypy` configuration correctly finds installed stub packages.
  Fix: Verify that your `mypy` configuration and environment allows it to discover installed packages supporting PEP 561. Generally, `mypy` should find them automatically if installed in the same environment.
• gotcha It is strongly recommended to import `mypy-boto3` types only within `if TYPE_CHECKING:` blocks to avoid adding stub packages as runtime dependencies. This keeps your production environment lighter.
  Fix: Wrap `from mypy_boto3_... import ...` statements in `if TYPE_CHECKING:` blocks and use forward references (string literal type hints) for type annotations.
• gotcha PyCharm users might experience slow performance and high CPU usage with `Literal` overloads due to a known issue (PY-40997). The project recommends using `boto3-stubs-lite` or disabling PyCharm's type checker and relying on `mypy` or `pyright` instead.
  Fix: Consider installing `boto3-stubs-lite[chime-sdk-meetings]` instead, or configure PyCharm to use an external type checker like `mypy` or `pyright`.

Install

• pip install mypy-boto3-chime-sdk-meetings Install standalone stub package
• pip install 'boto3-stubs[chime-sdk-meetings]' Install via boto3-stubs meta-package

Imports

• ChimeSDKMeetingsClient

  from typing import TYPE_CHECKING
  import boto3
  
  if TYPE_CHECKING:
      from mypy_boto3_chime_sdk_meetings.client import ChimeSDKMeetingsClient
  
  client: 'ChimeSDKMeetingsClient' = boto3.client('chime-sdk-meetings')

  It is best practice to use `if TYPE_CHECKING:` to avoid adding `mypy-boto3-*` packages as runtime dependencies. The type hint then uses a forward reference string.
• CreateMeetingRequestRequestTypeDef

  from typing import TYPE_CHECKING
  
  if TYPE_CHECKING:
      from mypy_boto3_chime_sdk_meetings.type_defs import CreateMeetingRequestRequestTypeDef
  
  request: 'CreateMeetingRequestRequestTypeDef' = {'ClientRequestToken': 'token', 'MediaRegion': 'us-east-1'}

Quickstart

This quickstart demonstrates how to use `mypy-boto3-chime-sdk-meetings` to get type hints for `boto3` calls related to Chime SDK Meetings. It initializes a client, creates a meeting, lists meetings, and then deletes the created meeting. The `if TYPE_CHECKING:` block ensures that the specific `mypy-boto3` imports are only processed by static type checkers, avoiding unnecessary runtime dependencies.

import os
from typing import TYPE_CHECKING

import boto3

# Ensure boto3 is installed: pip install boto3
# Ensure stubs are installed: pip install mypy-boto3-chime-sdk-meetings

if TYPE_CHECKING:
    from mypy_boto3_chime_sdk_meetings.client import ChimeSDKMeetingsClient
    from mypy_boto3_chime_sdk_meetings.type_defs import CreateMeetingResponseTypeDef

region = os.environ.get('AWS_REGION', 'us-east-1')

# The client variable gets type-hinted by mypy-boto3
client: 'ChimeSDKMeetingsClient' = boto3.client('chime-sdk-meetings', region_name=region)

try:
    # Example: Create a meeting
    meeting_id = 'my-unique-meeting-id'
    create_meeting_response: CreateMeetingResponseTypeDef = client.create_meeting(
        ClientRequestToken=meeting_id,
        MediaRegion='us-east-1',
        ExternalMeetingId='external-meeting-123'
    )
    print(f"Successfully created meeting: {create_meeting_response['Meeting']['MeetingId']}")

    # Example: List meetings (requires pagination for more results)
    list_meetings_response = client.list_meetings()
    print(f"Number of meetings: {len(list_meetings_response['Meetings'])}")

    # Example: Delete a meeting
    client.delete_meeting(MeetingId=create_meeting_response['Meeting']['MeetingId'])
    print(f"Successfully deleted meeting: {create_meeting_response['Meeting']['MeetingId']}")

except Exception as e:
    print(f"An error occurred: {e}")