sync: pyright 2023 04 03 #66
Merged
Conversation
This file contains hidden or 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
…e number of unique expressions that are affected by branch and loop nodes in the code flow graph. This addresses microsoft/pyright#4519.
…ed TypedDict types when the narrowed expression includes a member access subexpression. This addresses microsoft/pyright#4548.
…n of file names in the output diagnostic report in cases where diagnostics were completely suppressed for that file using the `--level` option. This addresses microsoft/pyright#4549.
… `bytes` values. In the negative case, we can assume that the type is `Literal[0]`, `Literal['']` or `Literal[b'']`.
…alue of type `NoneType` to `type[object]`. This addresses microsoft/pyright#4550.
…as used within an expression segment of an f-string. This addresses microsoft/pyright#4552.
…py. In the case where one or more arguments evaluate to Any but those arguments map to parameters whose types are the same, the first overload is selected. Only in cases where an Any argument produces ambiguous results is an Unknown result produced. This addresses microsoft/pyright#4546.
…de" configuration option. A directory wildcard pattern (**) was not handled correctly. This addresses microsoft/pyright#4553.
…and <literal> != X". These were never documented to work, and they were causing significant performance issues. Also reverted recent attempt to modify the code complexity algorithm, as this change is no longer necessary. This addresses microsoft/pylance-release#3886 (comment).
… a subsequent optimization.
…rdependencies between variables with inferred types. The optimization involves the introduction of an incomplete type generation count that is updated when a the type cache is updated in a way that could affect previously-calculated incomplete types. This addresses microsoft/pyright#4231.
…" in certain cases when using an assignment expression (walrus operator) in a loop. This addresses microsoft/pyright#4557.
… instance methods directly from a `None` instance. This addresses microsoft/pyright#4562.
…with different numbers of parameters and with with arguments that evaluate to `Any`. This addresses microsoft/pyright#4564.
…agnostic based on evaluation ordering.
…ults in the constraint solver. This addresses python/typing#1342.
Bumps [http-cache-semantics](https://github.com/kornelski/http-cache-semantics) from 4.1.0 to 4.1.1. - [Release notes](https://github.com/kornelski/http-cache-semantics/releases) - [Commits](kornelski/http-cache-semantics@v4.1.0...v4.1.1) --- updated-dependencies: - dependency-name: http-cache-semantics dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
… import x` where `x` is later referenced from an inner scope within the module. This addresses microsoft/pyright#4579.
… argument type to define its base classes. This addresses microsoft/pyright#4580.
…e evaluation when a lambda is evaluated with an incomplete "expected" type. This addresses microsoft/pyright#4567.
… when using an augmented assignment targeting a subscripted expression within a loop. This addresses microsoft/pyright#4855 (reply in thread).
…alue to stop working. This regression didn't affect the language server code paths. This addresses microsoft/pyright#4862.
Co-authored-by: Bill Schnurr <bschnurr@microsoft.com> Co-authored-by: HeeJae Chang <hechang@microsoft.com> Co-authored-by: Erik De Bonte <erikd@microsoft.com> Co-authored-by: Rich Chiodo <rchiodo@microsoft.com>
…pe annotation (and a placeholder body) to have an inferred return type of `None` when it should be `Unknown`. This addresses microsoft/pyright#4867 (reply in thread).
…patterns used in a `case` statement when the subject type includes a TypedDict with a discriminated field type (i.e. a field whose value is limited to a particular literal value). This addresses microsoft/pyright#4868.
…mitted when overriding a method that includes multiple keyword-only parameters. This addresses microsoft/pylance-release#4173.
…n callable with a tuple parameter where the tuple was of indeterminate length. Previously, this generated an error if the source type parameter was a tuple with zero elements. This addresses microsoft/pyright#4876.
…t B` where `x` is a tuple and `B` is a boolean literal `True` or `False`. This addresses part of microsoft/pyright#4875.
…x[I] is not B` where `x` is a tuple and `B` is an enum literal.
…w__` methods, as per guidance from PEP 698's author. This addresses microsoft/pyright#4823.
…property` decorator. This addresses microsoft/pyright#4877.
…parameter has an incorrect type annotation (not a subtype of the containing class) in an overloaded method. This addresses microsoft/pyright#4880.
… expression that accepts multiple generic callables, at least one of which is parameterized by a `ParamSpec`, where the generic types of the callables interact when being solved. This addresses microsoft/pylance-release#4182.
…nsforming certain types that include TypeVars.
…passed as an argument to another generic function multiple times. In such a case, the second (and subsequent) instances of the function must be given unique type parameters so they are distinguished from other instances of the same function. This addresses microsoft/pyright#4852.
…` to `BaseExceptionGroup`. This addresses microsoft/pylance-release#4183.
… tuples whose lengths are unknown. This addresses microsoft/pyright#4889.
… captured variables.
…ctor using bidirectional type inference on a generic class that defines a `__new__` method but no `__init__` method. This addresses microsoft/pyright#4890.
… type argument for an invariant type parameter. This addresses microsoft/pyright#4891.
…#4882) Co-authored-by: Eric Traut <eric@traut.com>
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.
No description provided.