Bump mypy from 1.7.1 to 1.8.0

[dependabot]

Bumps mypy from 1.7.1 to 1.8.0.

Changelog

Sourced from mypy's changelog.

Mypy Release Notes

Next release

Mypy 1.8

We’ve just uploaded mypy 1.8 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.

Type-checking Improvements

• Do not intersect types in isinstance checks if at least one is final (Christoph Tyralla, PR 16330)
• Detect that @final class without __bool__ cannot have falsey instances (Ilya Priven, PR 16566)
• Do not allow TypedDict classes with extra keywords (Nikita Sobolev, PR 16438)
• Do not allow class-level keywords for NamedTuple (Nikita Sobolev, PR 16526)
• Make imprecise constraints handling more robust (Ivan Levkivskyi, PR 16502)
• Fix strict-optional in extending generic TypedDict (Ivan Levkivskyi, PR 16398)
• Allow type ignores of PEP 695 constructs (Shantanu, PR 16608)
• Enable type_check_only support for TypedDict and NamedTuple (Nikita Sobolev, PR 16469)

Performance Improvements

• Add fast path to analyzing special form assignments (Jukka Lehtosalo, PR 16561)

Improvements to Error Reporting

• Don't show documentation links for plugin error codes (Ivan Levkivskyi, PR 16383)
• Improve error messages for super checks and add more tests (Nikita Sobolev, PR 16393)
• Add error code for mutable covariant override (Ivan Levkivskyi, PR 16399)

Stubgen Improvements

• Preserve simple defaults in function signatures (Ali Hamdan, PR 15355)
• Include __all__ in output (Jelle Zijlstra, PR 16356)
• Fix stubgen regressions with pybind11 and mypy 1.7 (Chad Dombrova, PR 16504)

Stubtest Improvements

• Improve handling of unrepresentable defaults (Jelle Zijlstra, PR 16433)
• Print more helpful errors if a function is missing from stub (Alex Waygood, PR 16517)
• Support @type_check_only decorator (Nikita Sobolev, PR 16422)
• Warn about missing __del__ (Shantanu, PR 16456)
• Fix crashes with some uses of final and deprecated (Shantanu, PR 16457)

Fixes to Crashes

• Fix crash with type alias to Callable[[Unpack[Tuple[Any, ...]]], Any] (Alex Waygood, PR 16541)
• Fix crash on TypeGuard in __call__ (Ivan Levkivskyi, PR 16516)
• Fix crash on invalid enum in method (Ivan Levkivskyi, PR 16511)
• Fix crash on unimported Any in TypedDict (Ivan Levkivskyi, PR 16510)

Documentation Updates

• Update soft-error-limit default value to -1 (Sveinung Gundersen, PR 16542)

... (truncated)

Commits

• 3b46750 remove +dev suffix from version
• c9bc833 Fix tests broken by hatchling (#16655)
• 60d30e3 Fix crash with type alias to Callable[[Unpack[Tuple[Any, ...]]], Any] (#16541)
• f53f422 Allow type ignores of PEP 695 constructs (#16608)
• 7c33e7c @​final class without bool cannot have falsey instances (#16566)
• c224da5 Do not intersect types in isinstance checks if at least one is final (#16330)
• d54cc35 Change example in test cases with no stubs available (#16513)
• eb1ee97 Update hashes in sync-typeshed.py following recent typeshed sync (#16600)
• 344298e Revert use of ParamSpec for functools.wraps
• 3e5d813 Revert typeshed ctypes change
• 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)

[pull-request-quantifier-deprecated]

This PR has 0 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : No Changes
Size       : +0 -0
Percentile : 0%

Total files changed: 1

Change summary by file extension:
.txt : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.