Pull Pylance with Pyright 1.1.391 #9673
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This comment has been minimized.
This comment has been minimized.
rchiodo
approved these changes
Jan 8, 2025
|
According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅ |
erictraut
deleted the
pull-pylance-with-pyright-1.1.391-20250108-044808
branch
erictraut
added a commit
that referenced
this pull request
Feb 23, 2025
* main: (119 commits) pull-pylance-with-pyright-1.1.392-20250121-190415 (#9734) Updated typeshed stubs to the latest version. Fixed a bug that results in incorrect handling of a "bare" ClassVar annotation either with or without an assignment. This addresses #9720. (#9724) Fixed a bug that results in a false positive "recursive type definition" error under certain circumstances when the number of declarations for a symbol exceeds the internal threshold of 16. This addresses #9721. (#9722) pull-pylance-with-pyright-1.1.392-20250115-224906 (#9715) pull-pylance-with-pyright-1.1.392-20250115-210905 (#9714) Changed the fallback type from Unbound to Unknown for the case where pyright determines that a symbol requires code flow analysis but the execution scope exceeds the cyclomatic complexity threshold. This partly addresses #9709. Published 1.1.392 Fixed bug that results in an "incompatible method override" false negative when overriding a method that uses class-scoped type parameters with a method that uses method-scoped type parameters. This addresses #9405. (#9707) Added support for bidirectional type inference for assignment statements that are assigning to an index expression that is subscripted by a slice. This addresses #9564. (#9705) Improved type narrowing for `issubclass` in the negative ("else") case when the subject type is `type` or `Any`. This addresses #9656. (#9704) Fixed bug that results in a spurious "incompatible method override" error when two subclasses with an overloaded method are combined using multiple inheritance. This addresses #9625. (#9700) Fixed bug that results in a spurious error when an assignment expression (walrus operator) is used as an argument to a constructor call when the constructor has both a `__new__` and `__init__` with differing bidirectional type inference contexts. This addresses #9659. (#9699) Fixed bug that results in an incorrect "overlapping overload" error message in certain cases involving parameters annotated with `Self`. This addresses #9662. (#9698) Improved error reporting for "async with" statement. Added check that return result of `__aexit__` is awaitable and improved error messages for the case where `__enter__`, etc. are present but have incorrect signatures. This addresses #9694. (#9697) Changed code that computes unescaped literal string type to convert CRLF to LF within multi-line triple-quoted strings so the behavior is consistent with runtime. This addresses #9681. (#9690) pull-pylance-with-pyright-1.1.391-20250108-044808 (#9673) Added missing syntax error check for positional argument that follows an unpacked keyword argument in a call expression. Also added a check for an unpack operator used within the first argument of a `cast` call. This addresses #9674. (#9675) fixed Uri to use value check rather than reference check. (#9665) Eliminated type evaluation order dependency that results from return type inference that involves recursion. This addresses #9642. (#9658) ... # Conflicts: # packages/pyright-internal/src/analyzer/typeEvaluator.ts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
analyzeshould have parse and bind all or open user files. make sure that's true at least for open files in tests