Bump pyright from 1.1.190 to 1.1.252

[dependabot]

Bumps pyright from 1.1.190 to 1.1.252.

Release notes

Sourced from pyright's releases.

Published 1.1.252

Bug Fix: Fixed a false positive error when the special form Unpack is used in a context other than a type annotation.

Bug Fix: Fixed bug that resulted in a crash (due to infinite recursion) in reference provider under certain circumstances involving symbol renames.

Enhancement: Added check for a dataclass member that lacks a type annotation but is assigned a field descriptor. This combination results in a runtime exception in the dataclass implementation.

Behavior Change: Increased maximum number of declarations (assignments) to consider when inferring the type of an unannotated variable. It was previously 16, but it is now 64.

Bug Fix: Fixed bug in lambda type evaluation so it properly detects and reports when its type is incomplete due to recursion.

Bug Fix: Fixed regression in code flow analysis that depends on NoReturn call evaluation.

Bug Fix: Improved handling of calls to overloads that return NoReturn. If all overloads are annotated with NoReturn, the call is now evaluated as NoReturn. Previously, only the last overload was considered.

Bug Fix: Fixed bug that causes false positive when the evaluated type of a default argument used within a base class must be specialized for a derived class.

Bug Fix: Reduced the max number of recursive inferred function return results from 16 to 12 to address a crash (stack overflow) that appears in the pylance telemetry.

Published 1.1.251

Bug Fix: Fixed a bug that results in a false positive when the return type annotation of a function requires code flow analysis to evaluate and a call expression is located on a code path between the function and the declared type referenced by the return type annotation. The fix is to skip "NoReturn" analysis in the code flow engine in this case (and several other similar cases) because it's not necessary. This has the added benefit of improving performance.

Bug Fix: Fixed misleading diagnostic message associated with reportUnnecessaryComparison check when != operator is used in the expression.

Bug Fix: Added logic to better handle the case where a symbol is defined multiple times with a TypeAlias declaration. This is an error condition, but it does occur in some stdlib type stubs if pyright is configured to use "All" for the "pythonPlatform" setting.

Enhancement: Improved type verifier so it can target submodules that are installed using an editable install mechanism.

Performance: Added small performance enhancement for protocol matching. When a protocol mismatch is detected, the remainder of the members are skipped if the caller hasn't requested detailed diagnostic information.

Performance: Added protocol matching optimization for the case where the source type and the destination protocol are both non-generic classes. In this case, we can safely cache the protocol relationship and shortcut future checks.

Bug Fix: Fixed bug in type narrowing logic for expressions of the form "X not in Y".

Bug Fix: Fixed a bug in the isinstance and issubclass type narrowing code paths. They were not handling nested tuples for the second argument.

Enhancement: Extended the "X in Y" type narrowing to support dict, defaultdict and OrderedDict classes.

Bug Fix: Fixed bug that resulted in a false positive error when using == or != operator with type(None).

Bug Fix: Fixed a bug that led to a false negative in some instances when assigning an inappropriate type to a TypedDict key.

Bug Fix: Fixed a bug that led to a false positive when assigning a value to an index expression where the base type of the index was inferred rather than declared.

Bug Fix: Fixed a bug in completion provider that resulted in incomplete member suggestions when a LiteralString type is used.

Bug Fix: Fixed a bug that resulted in a false positive error when evaluating an expression a + b where a is a LiteralString. For purposes of binary expression evaluation, LiteralString should act like a str.

Published 1.1.250

Behavior Change: Removed the assumption that deferred evaluation of annotations is enabled by default in Python 3.11. It looks like this won't be the case.

... (truncated)

Commits

• ac576bb Published 1.1.252
• b460345 Published 1.1.251
• 8a9b23b Published 1.1.250
• bb79688 Published 1.1.249
• e9189b5 Published 1.1.248
• f4383ab Published 1.1.247
• e0e07d3 Published 1.1.246
• ccc95e0 Published 1.1.245
• 80858f6 Published 1.1.244
• 00b8d86 Published 1.1.243
• 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 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 #118.