mypy-boto3-entityresolution 1.28.12

Type annotations for boto3.EntityResolution 1.28.12 service generated with mypy-boto3-builder 7.15.2

mypy-boto3-entityresolution

Type annotations for boto3.EntityResolution 1.28.12 service compatible with VSCode, PyCharm, Emacs, Sublime Text, mypy, pyright and other tools.

Generated by mypy-boto3-builder 7.15.2.

More information can be found on boto3-stubs page and in mypy-boto3-entityresolution docs.

See how it helps to find and fix potential bugs:

• mypy-boto3-entityresolution
  • How to install
    • VSCode extension
    • From PyPI with pip
  • How to uninstall
  • Usage
    • VSCode
    • PyCharm
    • Emacs
    • Sublime Text
    • Other IDEs
    • mypy
    • pyright
  • Explicit type annotations
    • Client annotations
    • Paginators annotations
    • Literals
    • Typed dictionaries
  • How it works
  • What's new
    • Implemented features
    • Latest changes
  • Versioning
  • Thank you
  • Documentation
  • Support and contributing

How to install

VSCode extension

Add AWS Boto3 extension to your VSCode and run AWS boto3: Quick Start command.

Click Modify and select boto3 common and EntityResolution.

From PyPI with pip

Install boto3-stubs for EntityResolution service.

# install with boto3 type annotations
python -m pip install 'boto3-stubs[entityresolution]'


# Lite version does not provide session.client/resource overloads
# it is more RAM-friendly, but requires explicit type annotations
python -m pip install 'boto3-stubs-lite[entityresolution]'


# standalone installation
python -m pip install mypy-boto3-entityresolution

How to uninstall

python -m pip uninstall -y mypy-boto3-entityresolution

Usage

VSCode

• Install Python extension
• Install Pylance extension
• Set Pylance as your Python Language Server
• Install boto3-stubs[entityresolution] in your environment:

python -m pip install 'boto3-stubs[entityresolution]'

Both type checking and code completion should now work. No explicit type annotations required, write your boto3 code as usual.

PyCharm

Install boto3-stubs-lite[entityresolution] in your environment:

python -m pip install 'boto3-stubs-lite[entityresolution]'`

Both type checking and code completion should now work. Explicit type annotations are required.

Use boto3-stubs package instead for implicit type discovery.

Emacs

• Install boto3-stubs with services you use in your environment:

python -m pip install 'boto3-stubs[entityresolution]'

• Install use-package, lsp, company and flycheck packages
• Install lsp-pyright package

(use-package lsp-pyright
  :ensure t
  :hook (python-mode . (lambda ()
                          (require 'lsp-pyright)
                          (lsp)))  ; or lsp-deferred
  :init (when (executable-find "python3")
          (setq lsp-pyright-python-executable-cmd "python3"))
  )

• Make sure emacs uses the environment where you have installed boto3-stubs

Type checking should now work. No explicit type annotations required, write your boto3 code as usual.

Sublime Text

• Install boto3-stubs[entityresolution] with services you use in your environment:

python -m pip install 'boto3-stubs[entityresolution]'

• Install LSP-pyright package

Type checking should now work. No explicit type annotations required, write your boto3 code as usual.

Other IDEs

Not tested, but as long as your IDE supports mypy or pyright, everything should work.

mypy

• Install mypy: python -m pip install mypy
• Install boto3-stubs[entityresolution] in your environment:

python -m pip install 'boto3-stubs[entityresolution]'`

Type checking should now work. No explicit type annotations required, write your boto3 code as usual.

pyright

• Install pyright: npm i -g pyright
• Install boto3-stubs[entityresolution] in your environment:

python -m pip install 'boto3-stubs[entityresolution]'

Optionally, you can install boto3-stubs to typings folder.

Type checking should now work. No explicit type annotations required, write your boto3 code as usual.

Explicit type annotations

Client annotations

EntityResolutionClient provides annotations for boto3.client("entityresolution").

from boto3.session import Session

from mypy_boto3_entityresolution import EntityResolutionClient

client: EntityResolutionClient = Session().client("entityresolution")

# now client usage is checked by mypy and IDE should provide code completion

Paginators annotations

mypy_boto3_entityresolution.paginator module contains type annotations for all paginators.

from boto3.session import Session

from mypy_boto3_entityresolution import EntityResolutionClient
from mypy_boto3_entityresolution.paginator import (
    ListMatchingJobsPaginator,
    ListMatchingWorkflowsPaginator,
    ListSchemaMappingsPaginator,
)

client: EntityResolutionClient = Session().client("entityresolution")

# Explicit type annotations are optional here
# Types should be correctly discovered by mypy and IDEs
list_matching_jobs_paginator: ListMatchingJobsPaginator = client.get_paginator("list_matching_jobs")
list_matching_workflows_paginator: ListMatchingWorkflowsPaginator = client.get_paginator(
    "list_matching_workflows"
)
list_schema_mappings_paginator: ListSchemaMappingsPaginator = client.get_paginator(
    "list_schema_mappings"
)

Literals

mypy_boto3_entityresolution.literals module contains literals extracted from shapes that can be used in user code for type checking.

from mypy_boto3_entityresolution.literals import (
    AttributeMatchingModelType,
    IncrementalRunTypeType,
    JobStatusType,
    ListMatchingJobsPaginatorName,
    ListMatchingWorkflowsPaginatorName,
    ListSchemaMappingsPaginatorName,
    ResolutionTypeType,
    SchemaAttributeTypeType,
    EntityResolutionServiceName,
    ServiceName,
    ResourceServiceName,
    PaginatorName,
)


def check_value(value: AttributeMatchingModelType) -> bool:
    ...

Typed dictionaries

mypy_boto3_entityresolution.type_defs module contains structures and shapes assembled to typed dictionaries for additional type checking.

from mypy_boto3_entityresolution.type_defs import (
    IncrementalRunConfigTypeDef,
    InputSourceTypeDef,
    IncrementalRunConfigOutputTypeDef,
    InputSourceOutputTypeDef,
    SchemaInputAttributeTypeDef,
    SchemaInputAttributeOutputTypeDef,
    DeleteMatchingWorkflowInputRequestTypeDef,
    DeleteMatchingWorkflowOutputTypeDef,
    DeleteSchemaMappingInputRequestTypeDef,
    DeleteSchemaMappingOutputTypeDef,
    ErrorDetailsTypeDef,
    GetMatchIdInputRequestTypeDef,
    GetMatchIdOutputTypeDef,
    GetMatchingJobInputRequestTypeDef,
    JobMetricsTypeDef,
    GetMatchingWorkflowInputRequestTypeDef,
    GetSchemaMappingInputRequestTypeDef,
    JobSummaryTypeDef,
    ListMatchingJobsInputListMatchingJobsPaginateTypeDef,
    ListMatchingJobsInputRequestTypeDef,
    ListMatchingWorkflowsInputListMatchingWorkflowsPaginateTypeDef,
    ListMatchingWorkflowsInputRequestTypeDef,
    MatchingWorkflowSummaryTypeDef,
    ListSchemaMappingsInputListSchemaMappingsPaginateTypeDef,
    ListSchemaMappingsInputRequestTypeDef,
    SchemaMappingSummaryTypeDef,
    ListTagsForResourceInputRequestTypeDef,
    ListTagsForResourceOutputTypeDef,
    OutputAttributeOutputTypeDef,
    OutputAttributeTypeDef,
    PaginatorConfigTypeDef,
    ResponseMetadataTypeDef,
    RuleOutputTypeDef,
    RuleTypeDef,
    StartMatchingJobInputRequestTypeDef,
    StartMatchingJobOutputTypeDef,
    TagResourceInputRequestTypeDef,
    UntagResourceInputRequestTypeDef,
    CreateSchemaMappingInputRequestTypeDef,
    CreateSchemaMappingOutputTypeDef,
    GetSchemaMappingOutputTypeDef,
    GetMatchingJobOutputTypeDef,
    ListMatchingJobsOutputTypeDef,
    ListMatchingWorkflowsOutputTypeDef,
    ListSchemaMappingsOutputTypeDef,
    OutputSourceOutputTypeDef,
    OutputSourceTypeDef,
    RuleBasedPropertiesOutputTypeDef,
    RuleBasedPropertiesTypeDef,
    ResolutionTechniquesOutputTypeDef,
    ResolutionTechniquesTypeDef,
    CreateMatchingWorkflowOutputTypeDef,
    GetMatchingWorkflowOutputTypeDef,
    UpdateMatchingWorkflowOutputTypeDef,
    CreateMatchingWorkflowInputRequestTypeDef,
    UpdateMatchingWorkflowInputRequestTypeDef,
)


def get_structure() -> IncrementalRunConfigTypeDef:
    return {...}

How it works

Fully automated mypy-boto3-builder carefully generates type annotations for each service, patiently waiting for boto3 updates. It delivers drop-in type annotations for you and makes sure that:

• All available boto3 services are covered.
• Each public class and method of every boto3 service gets valid type annotations extracted from botocore schemas.
• Type annotations include up-to-date documentation.
• Link to documentation is provided for every method.
• Code is processed by black and isort for readability.

What's new

Implemented features

• Fully type annotated boto3, botocore, aiobotocore and aioboto3 libraries
• mypy, pyright, VSCode, PyCharm, Sublime Text and Emacs compatibility
• Client, ServiceResource, Resource, Waiter Paginator type annotations for each service
• Generated TypeDefs for each service
• Generated Literals for each service
• Auto discovery of types for boto3.client and boto3.resource calls
• Auto discovery of types for session.client and session.resource calls
• Auto discovery of types for client.get_waiter and client.get_paginator calls
• Auto discovery of types for ServiceResource and Resource collections
• Auto discovery of types for aiobotocore.Session.create_client calls

Latest changes

Builder changelog can be found in Releases.

Versioning

mypy-boto3-entityresolution version is the same as related boto3 version and follows PEP 440 format.

Thank you

• Allie Fitter for boto3-type-annotations, this package is based on top of his work
• black developers for an awesome formatting tool
• Timothy Edmund Crosley for isort and how flexible it is
• mypy developers for doing all dirty work for us
• pyright team for the new era of typed Python

Documentation

All services type annotations can be found in boto3 docs

Support and contributing

This package is auto-generated. Please reports any bugs or request new features in mypy-boto3-builder repository.