Mypy-boto3-builder

Notes

- Supported services are no longer hardcoded, so new boto3 services are supported as soon as they are released
- Compatibility with `conda-forge` builds
- New daily sanity check for all generated packages to ensure stability

Added
- `[builder]` Supported services are no longer hardcoded
- `[builder]` `--list-services` CLI flag to output a list of supported services
- `[ci]` `Sanity check` workflow to check generated packages daily

Changed
- `[boto3-stubs]` Doc links now point to latest `boto3` docs
- `[botocore-stubs]` Doc links now point to latest `boto3` docs
- `[ci]` `check_output` runs tests with `mypy` as well
- `[boto3-stubs]` Requires non-strict versions of subpackages, five micro releases below the current (should fix `conda-forge` builds)
- `[docker]` Uses strict `regex==2021.7.6` package version
- `[builder]` Updated `black` and `isort`

Fixed
- `[boto3-stubs]` Removed Generics from `boto3.resouces.collection`
- `[builder]` Potential infinite recursion while working with paths
- `[builder]` Removed aggressive cleanup of unused generated files

Notes

This is an urgent bugfix, please update `boto3-stubs` from `1.17.103` to `1.17.103.post1`

Fixed
- `[services]` Collections are loosely typed again, they were broken in `4.22.0`
- `[builder]` Added `Python 3.10` classifier to all generated packages

Added
- `[boto3-stubs]` Fully annotated `boto3.s3.transfer`

Changed
- `[services]` `Client` is subclassed from `botocore.client.BaseClient` for compatibility with `botocore-stubs`
- `[services]` `Client.exceptions` is typed as a property as it should be

Fixed
- `[services]` Collections bases used to be loosely typed, now they are compatible with `botocore-stubs`
- `[botocore-stubs]` `BaseClient.get_waiter` annotation was not compatible with `boto3-stubs`
- `[botocore-stubs]` `BaseClient.get_paginator` annotation was not compatible with `boto3-stubs`
- `[botocore-stubs]` Removed `BaseClient.__getattr__` annotation because it hides `hash no attribute` type checking error
- `[botocore-stubs]` `ResourceCollection.__iter__` annotation was incorrect, now returns `Iterator[Resource]`
- `[builder]` Uses stricter output packages type checking with `pyright`
- `[builder]` Incorrect URLs to README images on PyPI page

Notes

TypeDefs changes introduced in `4.19.0` were too dramatic. In order to keep the package as backward-compatible as possible, TypeDefs changes are reverted.

Unfortunately, there is no way to keep things as they were because older versions used to add `ResponseMetadata` to TypeDefs that do not include it. So, this version adds `ResponseMetadataTypeDef` postfix to Response TypeDef only if there is a conflict. So, it should still be way closer to pre-`4.19.0` releases.

New packages `boto3-stubs 1.17.101.post2` and `boto3-stubs 1.17.102.post1` will be released shortly after.

Changed
- `[services]` Reverted `ResponseTypeDef` postfix for all Response Shapes from `4.19.0`
- `[services]` If both Shape and Response Shape are required, Response TypeDef gets `ResponseMetadataTypeDef` postfix

Added
- `[docs]` Added a short docstring to all annotated public methods

Changed
- `[services]` Request `datetime` arguments can be passed as timestamp `str` as long as `botocore` allows it
- `[services]` Response `blob` arguments always have a strict `bytes` or `StreamingBody` type
- `[docker]` Rebased to Alpine 3.13 and reduced image size

Fixed
- `[builder]` Removed outdated `setuptools` packaging
- `[builder]` Fixed missing package info on PyPI page
- `[builder]` Enforced `pyright` typing check
- `[docs]` Anchor links to `boto3` waiters documentation were incorrect

Notes

This version has a breaking change. If you use `type_defs.py` imports to annotate your code, you might have to change response type defs imports, e.g. `CopyObjectOutputTypeDef` -> `CopyObjectOutputResponseTypeDef`

Changes
Added
- `[services]` All methods now have Request TypeDefs to validate arguments passed as a Mapping
- `[services]` Client Request TypeDefs have `RequestTypeDef` name postfix
- `[services]` Resource Request TypeDefs have `<resource_name>RequestTypeDef` name postfix
- `[docs]` Methods have a link to Request TypeDef if it exists

Changed
- `[builder]` Response TypeDefs have `ResponseTypeDef` postfix to avoid name clash

Fixed
- `[services]` Output shapes are recognized by origin instead of name
- `[sagemaker]` `ResponseMetadata` does not appear in non-output shapes
- `[cognito-identity]` Name clash for `IdentityPoolTypeDef`, splitted to `IdentityPoolTypeDef` and `IdentityPoolResponseTypeDef`
- `[builder]` Validation for package name clashes was not working as expected
- `[services]` Slow-parsed methods are now keyword-only as well
- `[services]` Resource constructor methods are not keyword-only anymore, as `boto3` allows positional arguments