Bump pyright from 1.1.156 to 1.1.157

[dependabot]

Bumps pyright from 1.1.156 to 1.1.157.

Release notes

Sourced from pyright's releases.

Published 1.1.157

Bug Fix: Fixed false positive error when calling an object that has an Any in its inheritance chain.

Enhancement: Improved support for callable type narrowing in cases where the type is a non-callable instance, but a subtype could be callable.

Enhancement: Improved handling of callable type narrowing when the type involves a constrained type variable.

Enhancement: Added support for ParamSpec's within a Protocol, which is supported in Python 3.10.

Enhancement: Improved handling of isinstance type narrowing logic when the type being narrowed is a callable.

Bug Fix: Fixed recent regression in type evaluator that occurs when a generic (non-specialized) type is assigned to another generic type and the type parameter(s) for the generic type are invariant.

Bug Fix: Fixed bug that caused diagnostics from an open file not to be cleared after closing that file if it was not saved.

Enhancement (from pylance): Improved completion suggestions for literals when used as dictionary keys.

New Feature: Implemented "reportUninitializedInstanceVariable" diagnostic check that looks for instance variables that are not initialized in the class body or constructor.

Bug Fix: Fixed false positive error due to bug in constraint solver related to the handling of Type[T] when T is a constrained type variable.

Bug Fix: Fixed false positive error related to the use of a recursive type alias when from __future__ import annotations was in effect.

Bug Fix: Fixed false negative related to augmented assignment expressions when operand was a union type and a subset of the union subtypes were not supported for the operation.

Commits

• 5d791a0 Published 1.1.157
• 5718a71 Update dependencies, eliminate broken webpack plugin, begin browser refactori...
• See full diff 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 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)

[codecov]

Codecov Report

Merging #350 (ba2ceea) into main (5ea93ab) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #350   +/-   ##
=======================================
  Coverage   65.22%   65.22%           
=======================================
  Files           4        4           
  Lines         417      417           
  Branches       85       85           
=======================================
  Hits          272      272           
  Misses        129      129           
  Partials       16       16           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5ea93ab...ba2ceea. Read the comment docs.