Registry /
type-stubs / mypy-boto3-networkflowmonitor
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.8s · import 0.568s · 114MB
114MB installed
● package 114MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
NetworkFlowMonitorClient
✓ from mypy_boto3_networkflowmonitor import NetworkFlowMonitorClient
✗ from boto3.client import NetworkFlowMonitorClient
The client stub is imported directly from the `mypy_boto3_networkflowmonitor` package, not from `boto3`.
ListNetworkFlowMonitorsOutputTypeDef
✓ from mypy_boto3_networkflowmonitor.type_defs import ListNetworkFlowMonitorsOutputTypeDef
✗ from boto3.networkflowmonitor.type_defs import ListNetworkFlowMonitorsOutputTypeDef
Specific type definitions (e.g., for method outputs or input parameters) are found in the `type_defs` submodule.
This quickstart demonstrates how to initialize a `boto3` client for NetworkFlowMonitor and use the type stubs for improved static analysis with `mypy`. After installing, run this code (ensure AWS credentials are set up for `boto3`) and then run `mypy your_script_name.py` to see the type checking in action.
import boto3
from mypy_boto3_networkflowmonitor import NetworkFlowMonitorClient
from typing import TYPE_CHECKING
# Only import TypeDefs if you need them for specific annotations
if TYPE_CHECKING:
from mypy_boto3_networkflowmonitor.type_defs import (
ListNetworkFlowMonitorsOutputTypeDef,
)
def list_monitors():
# Instantiate the boto3 client, annotated with the stub type
client: NetworkFlowMonitorClient = boto3.client("network-flow-monitor")
# The 'response' object will now have type hints based on the stub
# For a real scenario, you might add error handling.
response = client.list_network_flow_monitors()
print(f"Found {len(response['NetworkFlowMonitorList'])} network flow monitors:")
for monitor in response['NetworkFlowMonitorList']:
print(f" - ARN: {monitor['NetworkFlowMonitorArn']}, Status: {monitor['Status']}")
if __name__ == "__main__":
# Ensure AWS credentials are configured for boto3
# (e.g., via AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, or ~/.aws/credentials)
list_monitors()
Debug
Known issues
breakingSupport for Python 3.8 has been removed from `mypy-boto3-builder` versions 8.12.0 and later, which affects all generated service stubs including `mypy-boto3-networkflowmonitor`.fixUpgrade your Python environment to version 3.9 or higher.
affects: mypy-boto3-builder >= 8.12.0 and corresponding `mypy-boto3-*` stub packages
gotchaThese type stubs require `mypy` (or another compatible type checker) to be installed and configured in your project to provide type checking benefits. Without `mypy`, they serve no runtime purpose.fixInstall `mypy` (e.g., `pip install mypy`) and integrate it into your development workflow, typically by running `mypy your_script.py` or configuring it in your `pyproject.toml`.
affects: All versions
gotchaType stubs are generated for specific `boto3`/`botocore` versions. Mismatching versions between your installed `boto3` and `mypy-boto3-networkflowmonitor` can lead to incorrect or missing type hints.fixEnsure your `boto3` and `mypy-boto3-networkflowmonitor` packages are kept as synchronized as possible. The `mypy-boto3-builder` attempts to manage compatible dependency versions, but manual verification might be needed.
affects: All versions
gotchaThe `mypy-boto3` ecosystem migrated to PEP 561-compliant packages. While this generally improves compatibility with type checkers and build tools, it might subtly affect very old or custom build environments.fixEnsure your packaging and type checking tools are up-to-date. No specific action is usually required, but be aware if you encounter unexpected packaging issues.
affects: mypy-boto3-builder >= 8.12.0 and corresponding `mypy-boto3-*` stub packages
Upgrade
Version history
1.43.0latest on PyPI · released Apr 29, 2026
Audit
Dependencies
boto3requiredProvides the runtime functionality that these type stubs annotate. Stubs are generated for specific boto3 versions, so keep them synchronized.
mypyoptionalRequired for static type checking using these stubs. Other type checkers might also work, but mypy is the primary target.