Bump pyright from 1.1.223 to 1.1.376

[dependabot]

Bumps pyright from 1.1.223 to 1.1.376.

Release notes

Sourced from pyright's releases.

Published 1.1.376

Bug Fixes:

• Fixed bug that results in a crash when an empty tuple is used to specialize a generic type alias parameterized by a ParamSpec.
• Fixed a bug that results in a false positive reportInconsistentOverload error when the implementation of the overload includes a decorator that changes the type of the implementation to a non-function type.
• Fixed bug that results in a false positive error when type argument for Literal doesn't follow type expression rules within a value expression context.
• Fixed regression that resulted in a hang when determining whether an overload implementation with generics was compatible with its overloads.
• Fixed bug that results in a false negative reportIncompatibleMethodOverride when the child class method uses a type parameter that is scoped to the child class.
• Fixed bug that produces signatures with extra (unnecessary) positional-only and keyword-only separators when using a TypedDict with zero fields.
• Improved consistency of parameter name restrictions for the reportSelfClsParameterName check. Previously, different rules were applied to __new__ and class methods within metaclasses.
• Fixed a false positive error when solving type variables in a call that involves a lambda.
• Fixed bug that results in a confusing type in an error message when isinstance type narrowing between a type and another type creates a subclass.
• Fixed bug that leads to false positive error when a protocol has a read-only property a class has a Final variable.
• Fixed bug that leads to a hang under certain circumstances involving deeply-nested higher-order functions.
• Fixed bug that results in a confusing type in an error message when isinstance type narrowing between a type and another type creates a subclass.

Enhancements:

• Enhanced argument-to-parameter matching logic to support dictionary unpacking where the dict key type is a union of literals.

Behavior Changes:

• Changed composition of settings that affect type checking behaviors. Previously, some LSP settings that affect type checking could override config files. Now, the config file always "wins". Command-line parameters passed to the CLI version of pyright win over both LSP settings and config files.
• Changed synthesized comparison methods (__lt__, etc.) for dataclasses when order=True to use Self rather than an instance of the class. This is not only more consistent with other synthesized methods, but it also preserves covariance of type variables if the dataclass is frozen.
• Changed behavior for protocols that have methods with method-scoped type variables. These are no longer treated as free type variables during protocol matching, so they can be used to support rank-2 polymorphism. This behavior is not currently dictated by the typing spec, but it is more consistent with mypy.

Published 1.1.375

Bug Fixes:

• Fixed bug that results in a false positive error when a covariant type variable that is scoped to a method is used in a parameter annotation.
• Fixed bug that leads to internal data structure corruption and subsequent false positive errors in certain cases involving unions of Unknown types that include type aliases.
• Fixed bug in the functools.partial logic that results in incorrect handling of an unpacked TypedDict when used with a **kwargs parameter.
• Fixed bug that results in a false positive reportUnsupportedDunderAll warning when using the __all__.extend(x.__all__) form and the list of entries in x is empty.
• Fixed bug in TypeVar auto-variance calculations for NamedTuples. Since NamedTuple variables are read-only, they should not cause a TypeVar to be invariant.
• Added subtyping support or IntEnum and StrEnum members. These literal values are subtypes of the corresponding literal int or str.
• Fixed bug that results in a false positive error under certain circumstances when passing an overloaded function as an argument to a call.
• Fixed bug that caused first argument of cast method on memoryview object to be treated as a type expression. Pyright was confusing this method with typing.cast.
• Fixed a bug that results in incorrect overload matching when one overload contains a zero-arity variant and another overload contains an *args (variadic) parameter.
• Fixed a bug that results in incorrect type narrowing for truthy/falsy type guards consisting of an Enum member when the enum class derives from ReprEnum. In this case, the "magic" of the enum implementation forwards the __bool__ call to the underlying value.
• Fixed a bug that results in incorrect type narrowing when using isinstance with an instance of a generic class as the first argument and a concrete subclass as the filter type.
• Fixed bug in type narrowing logic for value patterns, specifically when two enums with members of the same name are involved.
• Fixed bug that causes infinite recursion and memory exhaustion under certain circumstances involving recursive type aliases where the type alias is used as a type argument.

Enhancements:

• Updated typeshed stubs to the latest version.
• Added support for bool expansion to Literal[True] | Literal[False] during pattern matching when using value patterns.

Behavior Changes:

• Changed disableLanguageServices feature to apply to hover text as well as other language services. Previously, hover text was excluded.
• Allow Final and ClassVar to be combined in both directions within a dataclass. Previously, the Final qualifier needed to be the outermost.

Published 1.1.374

Note: This week's release includes some major changes related to TypeVar constraint solving that have been in the works for a while. These changes simplify the code, make constraint solving behaviors more consistent, and eliminate a number of false positive errors that were reported over the past year. However, these code changes produce different constraint solving behaviors in some cases. These extensive code changes also come with the potential of regressions. I've done extensive analysis of the type checking outputs across over a hundred public code bases, but it's possible that I've missed something. Please report any new behavior that you think is a bug.

... (truncated)

Commits

• 7fd5ed2 Published 1.1.376
• 07ca233 Updated typescript compiler version from 5.2 to 5.5.4 to avoid a bug I was hi...
• f0c0dc8 Published 1.1.375
• 5992d8a Published 1.1.374
• 258e275 Published 1.1.373
• d6372d4 Published 1.1.372
• 8f82d8d Published 1.1.371
• 93ac52f Published 1.1.370
• a5cbd47 Published 1.1.369
• 1bf99d3 Published 1.1.368
• 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)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.16%. Comparing base (2c00768) to head (8e52f20).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2502   +/-   ##
=======================================
  Coverage   90.15%   90.16%           
=======================================
  Files         247      247           
  Lines       15610    15610           
=======================================
+ Hits        14073    14074    +1     
+ Misses       1537     1536    -1     

see 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

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

[dependabot]

Superseded by #2519.