Option to ignore reportUninitializedInstanceVariable in stubs
#4137
Labels
addressed in next version
Issue is fixed and will appear in next published version
enhancement request
New feature or request
Comments
|
I agree that this check doesn't make sense for stub files. I've changed pyright to skip the check entirely for stubs. This will be included in the next release. |
erictraut
pushed a commit
that referenced
this issue
Nov 4, 2022
…n stub files. This addresses #4137.
erictraut
added
the
addressed in next version
|
This is included in pyright 1.1.279, which I just published. It will also be included in a future version of pylance. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
reportUninitializedInstanceVariableis raised in type stubs. Since there's not way to disable rules per folder or file-type, I have to disable it entirely or add# pyright: reportUninitializedInstanceVariable=falseat the top of all my stubs.Describe the solution you'd like
An option to ignore
reportUninitializedInstanceVariablein.pyifiles specifically.Additional context
A workaround is to add
=...but that does no comply with Typeshed's practices.Since both are valid, this is more of a stylistic choice. Enforcing it forces redundancy.
The text was updated successfully, but these errors were encountered: