build(deps): bump mypy from 1.6.1 to 1.7.1 in /requirements

[dependabot]

Bumps mypy from 1.6.1 to 1.7.1.

Changelog

Sourced from mypy's changelog.

Mypy Release Notes

Next release

Stubgen will now include __all__ in its output if it is in the input file (PR 16356).

Mypy 1.7

We’ve just uploaded mypy 1.7 to the Python Package Index (PyPI). Mypy is a static type checker for Python. This release includes new features, performance improvements and bug fixes. You can install it as follows:

python3 -m pip install -U mypy

You can read the full documentation for this release on Read the Docs.

Using TypedDict for **kwargs Typing

Mypy now has support for using Unpack[...] with a TypedDict type to annotate **kwargs arguments enabled by default. Example:

# Or 'from typing_extensions import ...'
from typing import TypedDict, Unpack
class Person(TypedDict):
name: str
age: int
def foo(**kwargs: Unpack[Person]) -> None:
...
foo(name="x", age=1)  # Ok
foo(name=1)  # Error

The definition of foo above is equivalent to the one below, with keyword-only arguments name and age:

def foo(*, name: str, age: int) -> None:
    ...

Refer to PEP 692 for more information. Note that unlike in the current version of the PEP, mypy always treats signatures with Unpack[SomeTypedDict] as equivalent to their expanded forms with explicit keyword arguments, and there aren't special type checking rules for TypedDict arguments.

This was contributed by Ivan Levkivskyi back in 2022 (PR 13471).

TypeVarTuple Support Enabled (Experimental)

Mypy now has support for variadic generics (TypeVarTuple) enabled by default, as an experimental feature. Refer to PEP 646 for the details.

TypeVarTuple was implemented by Jared Hance and Ivan Levkivskyi over several mypy releases, with help from Jukka Lehtosalo.

... (truncated)

Commits

• 6b3c418 Update version to 1.7.1 (without +dev)
• c10e173 [mypyc] Fix regression with nested functions (#16484)
• e6399d1 Fix polymorphic application for callback protocols (#16514)
• 661adb7 Fix crash on strict-equality with recursive types (#16483)
• 6c8e0cc Ignore position if imprecise arguments are matched by name (#16471)
• 5c354c4 Fix missing meet case exposed by len narrowing (#16470)
• 88791ca Exclude private attributes from override checks (#16464)
• 4b5b316 Special-case unions in polymorphic inference (#16461)
• f862d3e Fix crash on Callable self in call (#16453)
• fe79a59 Bump version to 1.7.1+dev
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[tvainika]

Is this used at all?

[aiven-anton]

I wrote this in a review too but apparently failed to press send:

---

I believe Map types should not have names: https://avro.apache.org/docs/1.10.2/spec.html#Maps. I believe a name only makes sense when the nested thing is something that can be referred to in one way or other, such as an Enum or nested Record type. Notably, it looks odd also that our ArrayType has a name.

I trust the backups suite excersises this well enough such that if we remove this and it passes, I'm comfortable.

[aiven-anton]

Also perhaps useful for reference, in the Python Avro implementation, MapSchema does not inherit NamedSchema, but EnumSchema does:

• https://github.com/apache/avro/blob/fd1433954f8344ffa433a42734e0dce1cd71deea/lang/py/avro/schema.py#L673
• https://github.com/apache/avro/blob/fd1433954f8344ffa433a42734e0dce1cd71deea/lang/py/avro/schema.py#L813

[matyaskuti]

Yeah, this isn't used. I wasn't sure if removing was okay, but I'll clear it up then!