Bump pyright from 1.1.190 to 1.1.250

[dependabot]

Bumps pyright from 1.1.190 to 1.1.250.

Release notes

Sourced from pyright's releases.

Published 1.1.249

Bug Fix: Fixed bug that resulted in incorrect type evaluation of a specialized type alias when the type argument contained a literal type. The literal was incorrectly widened to its non-literal form.

Bug Fix: Fixed bug that resulted in the incorrect type evaluation of member access expressions where the base type is type(None) (i.e. the NoneType class).

Enhancement: Enhanced the reportInvalidTypeVarUse check to report cases where a TypeVar found within a return type may go unsolved because it appears only within input parameters that have default argument values specified as .... In this situation, it is recommended that an overload is provided that specifies the return type when the default argument value is used by a caller.

Bug Fix: Fixed bug that resulted in a false positive when assigning a function or callable containing position-only parameters to a callable with a TypeVarTuple.

Bug Fix: Fixed bug that caused docstrings to be truncated to 32 characters when generating stubs.

Enhancement: Enhanced reportInvalidTypeVarUse to detect cases where a constructor (__init__ method) includes class-scoped TypeVars that may go unsolved because they are associated only with parameters that have default argument values.

Published 1.1.248

Enhancement: Added more complete validation of types used within a PEP 604-style union. Previously, the use of a P.args or P.kwargs type was not flagged as an error as it should be.

Bug Fix: Fixed bug that resulted in a false positive error when an await keyword was used with an operand that evaluated to a bound type variable.

Bug Fix: Fixed a bug that resulted in a false positive when using *args or **kwargs within a class argument list.

Enhancement: Improved special-case code for functools.totalordering so it enforces the operand type in the provided __lt__ method.

Bug Fix (from pylance): Honor the "hasWatchFileRelativePathCapabilities" of the client and don't use this facility if it's unsupported.

Bug Fix: Fixed a bug that caused dataclass_transform to fail when used on an overloaded function if it was not applied to the first overload.

Enhancement: Improved parse recovery for member access expressions that are missing the member name. This allows completion suggestions to work when a member access expression is used within a list comprehension.

Behavior Change: Changed reportInvalidStubStatement rule so it doesn't complain about call and augmented assignment expressions that perform allowed manipulations of the __all__ symbol.

Bug Fix: Fixed false positive type error that occurred when evaluating a call to a generic function parameterized with a ParamSpec and called within a loop construct.

Bug Fix: Fixed a bug that resulted in inconsistent type evaluation for a captured variable within a lambda or inner function when found within a loop.

Behavior Change: Updated dataclass_transform to support parameter name field_specifiers, which replaces the older parameter named field_descriptors. For now, we'll support both to retain backward compatibility with libraries that shipped with the older form.

Bug Fix: Fixed a bug that affected type evaluation of member access expressions when the LHS was a dataclass (or dataclass-like) class and the member was a field declared as a descriptor type.

Bug Fix: Fixed regression that resulted in a false positive error when checking for incompatible method overrides when the method contained local TypeVars.

Bug Fix: Fixed false positive "code too complex" error caused by a recent regression.

Bug Fix: Fixed bug in completion provider where it was emitting four spaces rather than using the predominant tab sequence when generating a multi-line completion suggestion for a method override.

Bug Fix: Fixed bug that resulted in a false positive error when using a super() call to invoke a constructor with a default argument value and a parameter that is annotated with a TypeVar.

Bug Fix: Fixed bug that resulted in incorrect type evaluation for a property access within a class when that property's getter has a generic return type.

Enhancement: Updated typeshed stubs to the latest version.

... (truncated)

Commits

• 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)

[dependabot]

Superseded by #115.