Registry /
type-stubs / mypy-boto3-iotfleetwise
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.646s · 52.2MB
glibcpy 3.10–3.95 runs
installs and imports cleanly · install 3.8s · import 0.600s · 53MB
50MB installed
● package 50MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
IoTFleetWiseClient
✓ from mypy_boto3_iotfleetwise.client import IoTFleetWiseClient
✗ from boto3.client import IoTFleetWiseClient
The client class for type hinting is imported directly from the stub package, not from boto3 itself, which returns a dynamically typed object.
CreateFleetRequestTypeDef
✓ from mypy_boto3_iotfleetwise.type_defs import CreateFleetRequestTypeDef
Type definitions for request/response bodies are available as TypedDicts.
This quickstart demonstrates how to use `mypy-boto3-iotfleetwise` with a `boto3` client for the IoT FleetWise service. It explicitly types the client and uses a `TypedDict` for the request payload to ensure full static type checking during development.
import boto3
from mypy_boto3_iotfleetwise.client import IoTFleetWiseClient
from mypy_boto3_iotfleetwise.type_defs import CreateFleetRequestTypeDef, CreateFleetResponseTypeDef
def create_iot_fleet(fleet_id: str, fleet_description: str, tags: list[dict]) -> CreateFleetResponseTypeDef:
client: IoTFleetWiseClient = boto3.client("iotfleetwise")
request_payload: CreateFleetRequestTypeDef = {
"fleetId": fleet_id,
"description": fleet_description,
"tags": tags,
}
try:
response: CreateFleetResponseTypeDef = client.create_fleet(**request_payload)
print(f"Successfully created fleet: {response['fleetArn']}")
return response
except client.exceptions.ConflictException:
print(f"Fleet '{fleet_id}' already exists.")
# Handle the case where the fleet already exists, e.g., get its details
return client.get_fleet(fleetId=fleet_id)
except Exception as e:
print(f"Error creating fleet: {e}")
raise
# Example usage (requires AWS credentials configured)
# Replace with actual desired values
# try:
# fleet_response = create_iot_fleet(
# fleet_id="my-example-fleet",
# fleet_description="Fleet for testing purposes",
# tags=[{"key": "Environment", "value": "Dev"}]
# )
# print(f"Fleet details: {fleet_response}")
# except Exception as e:
# print(f"An error occurred: {e}")
Debug
Known issues
breakingPython 3.8 support was removed for all `mypy-boto3` stub packages, including `mypy-boto3-iotfleetwise`, starting with `mypy-boto3-builder` version 8.12.0. Users on Python 3.8 must upgrade to Python 3.9+ or pin an older version of the stub package.fixUpgrade your Python environment to 3.9 or higher. If upgrading is not possible, explicitly install an older compatible version, e.g., `pip install mypy-boto3-iotfleetwise==1.41.0`.
affects: >=1.42.0
breaking`mypy-boto3` packages migrated to PEP 561 compliant distribution in `mypy-boto3-builder` version 8.12.0. While this improves standard compatibility, users with highly customized `mypy` configurations or unusual import patterns might need to adjust their setup.fixEnsure `mypy` is up-to-date. In most cases, this change is transparent. If issues arise, consult `mypy` and `mypy-boto3` documentation on stub discovery and PEP 561 compliance. [cite: github_release_8.12.0, 18]
affects: >=1.42.0
breakingTypeDef naming conventions were changed in `mypy-boto3-builder` version 8.9.0. This includes shortening some TypeDef names (e.g., `CreateDistributionRequestRequestTypeDef` to `CreateDistributionRequestTypeDef`) and moving postfixes (e.g., `CreateDistributionExtraRequestTypeDef` to `CreateDistributionRequestExtraTypeDef`). Code explicitly importing or referencing these `TypedDict` names will break.fixUpdate imports and references to TypeDef names to reflect the new conventions. Review the specific service's `type_defs` module documentation for updated names.
affects: >=1.35.0 (approx, based on builder 8.9.0)
gotchaThese packages provide only type stubs for `boto3`; they do not include the `boto3` runtime library itself. `boto3` must be installed separately for your Python code to execute successfully.fixAlways ensure `boto3` is installed alongside `mypy-boto3-iotfleetwise` using `pip install boto3 mypy-boto3-iotfleetwise`.
affects: All versions
gotchaFor optimal type inference and auto-completion, especially in certain IDEs (e.g., older VS Code setups) or when using `boto3-stubs-lite`, explicit type annotations for `boto3.client()` and `boto3.session.client()` calls are recommended.fixAlways annotate the client variable with the specific client type from the stub package, e.g., `client: IoTFleetWiseClient = boto3.client("iotfleetwise")`. affects: All versions
Upgrade
Version history
1.43.0latest on PyPI · released Apr 29, 2026
Audit
Dependencies
boto3requiredRuntime dependency for the actual AWS SDK functionalities these stubs type-check.
mypyoptionalRequired for static type checking; these are type stubs designed for mypy.