chore(deps-dev): bump pyright from 1.1.350 to 1.1.359

[dependabot]

Bumps pyright from 1.1.350 to 1.1.359.

Release notes

Sourced from pyright's releases.

Published 1.1.359

Enhancements:

• Expanded support for len(x) == L type guard pattern (where x is a tuple) to support <, <=, > and >= comparisons as well.
• Improved some diagnostic messages, moving away from the term "member" to prefer "attribute". Switched from "cannot assign to type" to "incompatible with type" for consistency and clarity.
• Extended type narrowing logic for in and not in operators that target TypedDicts to also support constrained TypeVars that use TypedDicts as value constraints.
• Added a check for the case where a frozen dataclass overrides a field from its parent class but doesn't provide a default value (where its parent does). This can result in a type violation if the parent's default value is not compatible with the child's (covariant) field type.

Behavior Changes:

• Changed behavior when evaluating the upper bound expression, value constraints expression, or default expression for a PEP-695 type parameter. At runtime, these are always evaluated in a deferred manner even if they are not quoted. Pyright now follows the runtime behavior.
• Modified handling of annotated self parameter in __init__ method when evaluating constructor call so pyright conforms to the latest typing spec.
• Added missing check for the errant use of class-scoped type variables in a type annotation for the "self" parameter within an "init" method. The typing spec now clarifies that this is illegal and should generate an error.
• Updated logic for converting a class constructor to a callable to conform to the newly-updated typing spec.
• Changed the behavior when invoking constructor for type[T] where T is a TypeVar with no explicit upper bound (and therefore has an implicit upper bound of object). According to the newly-clarified typing spec, this should enforce the constructor signature of object.
• Modified behavior in constructor call code that previously applied some (now non-compliant) heuristics to reconcile a metaclass __call__ method with a __new__ method. The new behavior is now compliant with the typing spec.
• Changed behavior of conversion from class constructor to callable to conform with the typing spec in the case where the __new__ method of the class returns a value that indicates the __init__ method should be ignored.
• Changed behavior of conversion from class constructor to callable to conform to honor the annotated type of self in the __init__ method.
• Changed behavior of conversion from class constructor to callable to conform to honor return type of the __new__ method.

Bug Fixes:

• Fixed a bug that leads to inconsistent behaviors when an assignment leads to a type violation. When assigning to a local variable, the target expression is not "narrowed" to include the assigned type in this case. The new behavior applies this same behavior when assigning to instance or class variables.
• Fixed recent regression that results in a false positive error when applying a @property decorator to a method that has already had a decorator applied to it.
• Fixed bug that results in a spurious reportAbstractUsage error when an abstract class is captured through a type[T].
• Fixed bug that results in incorrect type evaluation when solving a ParamSpec type when there are multiple constraints provided.
• Fixed a bug that results in incorrect type evaluation when assigning a function with a NoReturn return type to a Callable[..., T].
• Fixed a bug that leads to a false negative when an unparenthesized assignment expression is used in a dictionary key within a dictionary expression or comprehension.
• Fixed bug that results in false positive error under certain circumstances that involve unions of TypeVars in an invariant context.

Published 1.1.358

Bug Fixes:

• (from Pylance): Fixed a bug that caused a crash under certain circumstances when an import cannot be resolved.
• Fixed non-compliance issue with TypeIs, which is documented to have an invariant type parameter.
• Fixed a bug that results in incorrect type evaluation when a sequence pattern in a match statement includes a * element and the subject includes a tuple with an element with indeterminate length.
• Fixed bug that results in an intermittent false positive "circular dependency" error for fields within a dataclass.
• Fixed a bug that results in a false positive error under certain circumstances when a TypeVar or TypeVarTuple is being solved with literal values in both an invariant and non-invariant context.
• Fixed bug that results in incorrect type evaluation in cases where a generic function returns a callable, and the function is called with a higher-order generic function as an argument.
• Fixed a bug that results in a false negative when a generic function returns a Callable type that is specialized to include a live (in-scope) type variable.
• Fixed bug that results in inconsistent type narrowing on assignment based on whether the assignment occurs within the same statement that includes the (declared) type annotation for the variable and whether the type annotation is provided as a type comment.

Enhancements:

• Added optimization for TypedDict type assignments. Under certain circumstances (e.g. when comparing large unions of TypedDict types), this can save significant time.
• Modified the handling of enum class attributes so those with private (mangled) names are exempted from being considered enum members. This reflects the runtime behavior.
• Added support for narrowing of subject subexpression within a match statement for references to the subexpression after the completion of the match statement.
• Updated typeshed stubs to the latest version.
• Improved error handling for quoted annotations. Bytes, raw strings, and f-strings are not allowed according to the typing spec.
• Added an error message for a Literal type annotation that includes a string with a named unicode escape sequence. These are not supported.

Published 1.1.357

Bug Fixes:

• Fixed bug that results in a false positive error when explicitly calling __new__ on a dataclass, namedtuple, or TypedDict. These classes all require synthesized __new__ methods.
• Fixed bug that results in false negative when a __new__ or __init__ method cannot be bound without a type violation.

... (truncated)

Commits

• cc3467f Published 1.1.359
• 989ee29 Published 1.1.358
• 8752be7 Published 1.1.357
• 4106a09 Share heap usage numbers to support cache cleanup in VS code (#7605)
• 9f02004 Published 1.1.356
• a2831b7 Published 1.1.355
• 0a73f4b Published 1.1.354
• 114501e Published 1.1.353
• ab40240 Drop support for node 12 (#7375)
• 08397a0 Published 1.1.352
• 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)

[dependabot]

Superseded by #239.