Registry /
type-stubs / mypy-boto3-servicecatalog-appregistry
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
muslpy 3.10–3.95 runs
installs and imports cleanly · install 0.0s · import 0.610s · 116.6MB
glibcpy 3.10–3.95 runs
installs and imports cleanly · install 5.9s · import 0.570s · 114MB
114MB installed
● package 114MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
AppRegistryClient
✓ from mypy_boto3_servicecatalog_appregistry.client import AppRegistryClient
✗ from mypy_boto3_servicecatalog_appregistry import AppRegistryClient
Client types are located in the '.client' submodule for clarity and to avoid name clashes.
AppRegistryServiceResource
✓ from mypy_boto3_servicecatalog_appregistry.service_resource import AppRegistryServiceResource
Service resource types (if available for the service) are in the '.service_resource' submodule.
ApplicationSummaryTypeDef
✓ from mypy_boto3_servicecatalog_appregistry.type_defs import ApplicationSummaryTypeDef
✗ from mypy_boto3_servicecatalog_appregistry.app_registry_client import ApplicationSummaryTypeDef
All core TypeDefs (input/output dictionaries for service operations) are consolidated in the '.type_defs' submodule.
This quickstart demonstrates how to obtain a type-hinted `AppRegistryClient` from `boto3` and use it to call an API operation. It also shows how to import and use response `TypeDef` objects for more granular type checking, typically under a `TYPE_CHECKING` guard.
import boto3
from mypy_boto3_servicecatalog_appregistry.client import AppRegistryClient
from typing import TYPE_CHECKING
# For advanced type checking of response objects
if TYPE_CHECKING:
from mypy_boto3_servicecatalog_appregistry.type_defs import CreateApplicationResponseTypeDef
def create_example_application(app_name: str, app_description: str):
# boto3 client is untyped by default
client = boto3.client(
"servicecatalog-appregistry",
aws_access_key_id="AKIATEST", # Using dummy creds for example
aws_secret_access_key="SECRET",
region_name="us-east-1"
)
# Type hint the client for mypy
typed_client: AppRegistryClient = client
# With the typed_client, autocompletion and type checking work
response = typed_client.create_application(
name=app_name,
description=app_description
)
# TYPE_CHECKING guard ensures this import is only for static analysis
if TYPE_CHECKING:
response_typed: CreateApplicationResponseTypeDef = response
print(f"Application ID: {response_typed['application']['id']}")
else:
print(f"Application ID: {response['application']['id']}")
# To run this example, replace dummy creds and provide a unique application name
# create_example_application("MyUniqueApp", "Managed by mypy-boto3 example")
Debug
Known issues
breakingDropped support for Python 3.8. Packages generated with `mypy-boto3-builder` version 8.12.0 and newer (including this package) now require Python 3.9 or higher.fixUpgrade your Python environment to 3.9 or newer.
affects: mypy-boto3-builder >= 8.12.0, mypy-boto3-servicecatalog-appregistry >= 1.42.0
breakingTypeDef naming conventions changed in builder version 8.9.0. Argument TypeDefs might have shorter names (e.g., `CreateRequestRequestTypeDef` -> `CreateRequestTypeDef`), and `Extra` postfixes were moved (e.g., `CreateExtraRequestTypeDef` -> `CreateRequestExtraTypeDef`).fixReview your TypeDef imports and usages after upgrading, adjusting names as per the new conventions (check generated `.type_defs.pyi` for specific service changes).
affects: mypy-boto3-builder >= 8.9.0
gotchaMigration to PEP 561 compliance. While generally an improvement, some older type-checking setups or tools might require updates to correctly discover and utilize the type stubs.fixEnsure your `mypy` configuration and project structure align with standard Python package and type stub discovery mechanisms. No code change is typically required in user applications.
affects: mypy-boto3-builder >= 8.12.0
gotchaLegacy `mypy-boto3` packages (pre-8.9.0 builder) were merged into `boto3-stubs`. If you're upgrading from very old `mypy-boto3` versions, ensure you're installing the correct new `mypy-boto3-*` package structure.fixVerify that your `pip install` commands specify the `mypy-boto3-*` package names, which are the current standard for individual service stubs.
affects: mypy-boto3-builder >= 8.9.0
gotchaAWS service names can change or be deprecated (e.g., `sms-voice` was replaced by `pinpoint-sms-voice`). This means the corresponding `mypy-boto3` package name will also change, requiring updates to your dependencies and imports.fixAlways refer to the official AWS documentation for the latest service names. If a service package is deprecated, follow the recommended migration path to the new service and its corresponding `mypy-boto3` stub package.
affects: All versions
Upgrade
Version history
1.43.0latest on PyPI · released Apr 29, 2026
Audit
Dependencies
boto3requiredProvides the AWS SDK for Python that these type stubs enhance. Users typically install the `boto3` version matching the `mypy-boto3-*` stub version.
mypyoptionalThe primary static type checker for which these annotations are designed. Required for leveraging the type-checking benefits.
pythonrequiredmypy-boto3 packages built with builder 8.12.0+ require Python 3.9 or newer.