Registry / type-stubs / mypy-boto3-migrationhuborchestrator

mypy-boto3-migrationhuborchestrator

library1.43.0pypypi✓ verified 22d ago

mypy-boto3-migrationhuborchestrator provides type annotations for the `boto3` AWS Migration Hub Orchestrator service, enhancing static analysis and IDE autocompletion for Python projects. It is generated by the `mypy-boto3-builder` and is currently at version 1.42.3, with releases closely tracking `boto3` updates to ensure compatibility and comprehensive type coverage.

type-stubs aws

pip install mypy-boto3-migrationhuborchestrator

github ↗package ↗docs ↗

INSTALL

IMPORT

SIG · MYPY-BOTO3-MIGRATI

mypy-boto3-migrationhuborchestrator

type-stubspythonv1.43.0

Install

4.0s avg

Import

11ms

Disk

18MB

Pass rate

10/ 10

Env Coverage10 / 10

glibc

3.9–3.13

musl

3.9–3.13

Install & Compatibility

Where this runs

tested against v1.43.0 · 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

musl

py 3.10–3.910 runs

installs and imports cleanly · install 0.0s · import 0.012s · 19.8MB

glibc

py 3.10–3.910 runs

installs and imports cleanly · install 4.0s · import 0.006s · 20MB

18MB installed

● package 18MB

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

MigrationHubOrchestratorClient

✓ from typing import TYPE_CHECKING if TYPE_CHECKING: from mypy_boto3_migrationhuborchestrator import MigrationHubOrchestratorClient

It is best practice to guard type imports with `if TYPE_CHECKING:` to avoid introducing runtime dependencies.

TemplateSummaryTypeDef

✓ from typing import TYPE_CHECKING if TYPE_CHECKING: from mypy_boto3_migrationhuborchestrator.type_defs import TemplateSummaryTypeDef

Type definitions (TypedDicts) for API responses are available in the `type_defs` submodule.

This quickstart demonstrates how to use the `mypy-boto3-migrationhuborchestrator` stubs with a `boto3` client to get type-checking for the `list_templates` operation. It includes the recommended `TYPE_CHECKING` guard for imports and handles potential `AccessDeniedException`.

import boto3 from typing import TYPE_CHECKING # Best practice: guard type imports with if TYPE_CHECKING if TYPE_CHECKING: from mypy_boto3_migrationhuborchestrator import MigrationHubOrchestratorClient from mypy_boto3_migrationhuborchestrator.type_defs import TemplateSummaryTypeDef # Initialize a boto3 client for Migration Hub Orchestrator client: MigrationHubOrchestratorClient = boto3.client('migrationhuborchestrator') # Use a method and check its return type try: response = client.list_templates(maxResults=5) templates: list[TemplateSummaryTypeDef] = response['Templates'] for template in templates: print(f"Template ID: {template['Id']}, Name: {template['Name']}") except client.exceptions.AccessDeniedException: print("Access denied. Please check your AWS credentials and permissions.") except Exception as e: print(f"An unexpected error occurred: {e}") # To run mypy: # 1. pip install mypy boto3 mypy-boto3-migrationhuborchestrator # 2. mypy your_script_name.py

Debug

Known issues

breakingStarting with `mypy-boto3-builder` version 8.12.0 (which generated this package), Python 3.8 is no longer supported for generated stub packages.

fix

Upgrade your Python environment to 3.9 or newer.

affects: mypy-boto3-builder >= 8.12.0 (and dependent stub packages like this one)

breakingIn `mypy-boto3-builder` version 8.9.0, type definition (TypeDef) naming conventions changed. This includes shorter names for packed method arguments and revised postfix handling for conflicting `TypeDef` names (e.g., `CreateDistributionExtraRequestTypeDef` became `CreateDistributionRequestExtraTypeDef`).

fix

Update your code to use the new `TypeDef` names as per the latest stub documentation. Your IDE or type checker should flag these if you are using explicit type hints.

affects: mypy-boto3-builder >= 8.9.0 (and dependent stub packages)

gotchaType imports from `mypy_boto3_*` packages should ideally be placed within `if TYPE_CHECKING:` blocks. This ensures that these stub packages are only used by static analysis tools (like mypy) and are not treated as runtime dependencies by your application, reducing the deployed package size.

fix

Wrap your `from mypy_boto3_* import ...` statements in `if TYPE_CHECKING:` blocks. For example: `from typing import TYPE_CHECKING; if TYPE_CHECKING: from mypy_boto3_migrationhuborchestrator import MigrationHubOrchestratorClient`.

affects: All versions

gotchaFollowing the migration to PEP 561 packages in `mypy-boto3-builder` 8.12.0, ensure your `mypy` or other type checker is up-to-date. Older versions might not correctly discover or utilize the stubs, leading to `Missing type stub` errors or incorrect type inference.

fix

Update your type checker (e.g., `pip install --upgrade mypy`) and ensure it's configured to recognize PEP 561-compliant stub packages.

affects: mypy-boto3-builder >= 8.12.0 (and dependent stub packages)

Errors

Common errors & fixes

ModuleNotFoundError: No module named 'mypy_boto3_migrationhuborchestrator'

The `mypy-boto3-migrationhuborchestrator` package has not been installed in your Python environment.

fix

Install the package using pip: `pip install mypy-boto3-migrationhuborchestrator`

Missing type stub for "mypy_boto3_migrationhuborchestrator" (reportMissingModuleStubs)

Your type checker (e.g., mypy or pyright) cannot find the installed type stubs, possibly due to an outdated type checker or incorrect configuration.

fix

Ensure your type checker is up-to-date (`pip install --upgrade mypy`) and correctly configured to discover PEP 561-compliant stub packages. Also, verify the package is installed in the environment being checked.

NameError: name 'MigrationHubOrchestratorClient' is not defined

Type imports from `mypy_boto3_*` packages are typically guarded by `if TYPE_CHECKING:` to avoid runtime dependencies, making them unavailable at runtime if not handled appropriately.

fix

Wrap your type imports in a `if TYPE_CHECKING:` block, and for runtime use, ensure `boto3` is used directly or provide a runtime-compatible fallback. For example: `from typing import TYPE_CHECKING; if TYPE_CHECKING: from mypy_boto3_migrationhuborchestrator import MigrationHubOrchestratorClient`.

error: Name 'OldMigrationHubOrchestratorTypeDef' is not defined

This error occurs because of a breaking change in `mypy-boto3-builder` version 8.9.0, which revised the naming conventions for `TypeDef` (TypedDict) objects, meaning older names are no longer recognized.

fix

Update your code to use the new `TypeDef` names. Consult the latest stub documentation for the correct naming conventions, which your IDE or type checker should also flag if you are using explicit type hints. For instance, `CreateDistributionExtraRequestTypeDef` became `CreateDistributionRequestExtraTypeDef` in a general example for the builder.

Upgrade

Version history

1.43.0latest on PyPI · released Apr 29, 2026

Audit

Dependencies

boto3requiredRuntime dependency for actual AWS interactions.

mypyoptionalThe static type checker that utilizes these annotations.

Agent activity

22 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/youtype/mypy_boto3_builder ↗

packagehttps://pypi.org/project/mypy-boto3-migrationhuborchestrator/ ↗

docshttps://youtype.github.io/boto3_stubs_docs/mypy_boto3_migrationhuborchestrator/ ↗