[ty] Implicit instance attributes declared Final
#19462
Merged
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.
Summary
Adds proper type inference for implicit instance attributes that are declared with a "bare"
Finaland addsinvalid-assignmentdiagnostics for all implicit instance attributes that are declaredFinalorFinal[…].Test Plan
New and updated MD tests.
Ecosystem analysis
pytest (https://github.com/pytest-dev/pytest) + error[invalid-return-type] src/_pytest/fixtures.py:1662:24: Return type does not match returned value: expected `Scope`, found `Scope | (Unknown & ~None & ~((...) -> object) & ~str) | (((str, Config, /) -> Unknown) & ~((...) -> object) & ~str) | (Unknown & ~str)The definition of the
scopeattribute is here. Looks like this is a new false positive due to missingTypeAliassupport that is surfaced here because we now infer a more precise type forFixtureDef._scope.