mypy-boto3-partnercentral-selling Type Annotations

1.42.80 · active · verified Sat Apr 11

mypy-boto3-partnercentral-selling provides type annotations for the `boto3` PartnerCentralSellingAPI service. It enables static type checking for `boto3` client calls, methods, and responses, enhancing code reliability and developer experience. The current version is 1.42.80, and it is frequently updated to align with `boto3` and AWS API changes.

Warnings

breaking As of `mypy-boto3-builder` version 8.12.0, support for Python 3.8 has been removed across all `mypy-boto3` packages, including `mypy-boto3-partnercentral-selling`.
Fix: Upgrade your Python environment to 3.9 or higher to continue receiving updates and full type-checking support. If stuck on Python 3.8, pin `mypy-boto3-builder` and related packages to versions <= 8.11.x.
gotcha The `mypy-boto3-*` packages provide *only* type annotations. You must have the `boto3` library itself installed for runtime functionality. They are not a replacement for `boto3`.
Fix: Ensure both `boto3` and the specific `mypy-boto3-<service>` stub package are installed via `pip install boto3 mypy-boto3-partnercentral-selling`.
gotcha It is crucial to keep your `mypy-boto3-*` stub packages in sync with your `boto3` library version. Mismatched versions can lead to incorrect type hints or `mypy` errors if API definitions have changed.
Fix: Periodically update both `boto3` and all `mypy-boto3-*` packages together (e.g., `pip install --upgrade boto3 mypy-boto3-partnercentral-selling`). Consider using a dependency management tool to pin versions.
breaking Starting with `mypy-boto3-builder` 8.9.0, some generated `TypeDef` names were shortened (e.g., `CreateDistributionRequestRequestTypeDef` -> `CreateDistributionRequestTypeDef`) or had conflicting postfixes moved (`CreateDistributionExtraRequestTypeDef` -> `CreateDistributionRequestExtraTypeDef`). While `partnercentral-selling` might not be directly affected by these *specific* examples, be aware that explicit imports of `TypeDef` objects might require updates.
Fix: If you explicitly import and use specific `TypeDef` classes from `mypy_boto3_partnercentral_selling.type_defs`, verify their names after upgrading `mypy-boto3`.
gotcha As of `mypy-boto3-builder` 8.12.0, all packages migrated to PEP 561-compliant distribution. This means the type information is now directly within the installed package structure. While generally beneficial, older type checkers or unusual import configurations might need adjustment.
Fix: Ensure your `mypy` configuration correctly finds type stubs for installed packages. Standard `mypy` setup should work automatically, but if you encounter 'module not found' errors for types, check `mypy`'s `MYPYPATH` or `[tool.mypy]` configuration.

Install

pip install boto3 mypy-boto3-partnercentral-selling Install `boto3` and type stubs

Imports

PartnerCentralSellingAPIClient
```
from mypy_boto3_partnercentral_selling.client import PartnerCentralSellingAPIClient
```
This is the primary way to import the type for the PartnerCentralSellingAPI boto3 client.
ServiceResource
```
from mypy_boto3_partnercentral_selling.service_resource import PartnerCentralSellingAPIResource
```
If using service resources (less common for this specific service), this provides its type.

Quickstart

This quickstart demonstrates how to obtain a type-hinted `boto3` client for PartnerCentralSellingAPI and use it. The `mypy-boto3-partnercentral-selling` package provides the necessary type stubs, allowing tools like MyPy to validate your AWS API calls and responses statically.

import boto3
from mypy_boto3_partnercentral_selling.client import PartnerCentralSellingAPIClient
from typing import TYPE_CHECKING

# Recommended: Use TYPE_CHECKING for imports only used by type checkers
if TYPE_CHECKING:
    # Only import if you need specific TypeDefs for complex scenarios
    from mypy_boto3_partnercentral_selling.type_defs import GetPartnerAccountOutputTypeDef

def get_partnercentral_selling_client() -> PartnerCentralSellingAPIClient:
    # boto3.client returns the actual client, which is type-checked by mypy-boto3-*
    return boto3.client("partnercentral-selling")

client: PartnerCentralSellingAPIClient = get_partnercentral_selling_client()

try:
    # Example API call with type-hinted client
    # Replace 'YOUR_PARTNER_ACCOUNT_ID' with a real one for a runnable example
    response = client.get_partner_account(partnerAccountId=os.environ.get('PARTNER_ACCOUNT_ID', 'YOUR_PARTNER_ACCOUNT_ID'))

    print(f"Partner account name: {response.get('partnerAccountName')}")
    print(f"Account status: {response.get('accountStatus')}")

except client.exceptions.ResourceNotFoundException:
    print("Partner account not found.")
except Exception as e:
    print(f"An error occurred: {e}")

view raw JSON →