This repository was archived by the owner on Apr 14, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
Use-before-def reported for class fields without default values #395
Description
Activity
The analyzer only offers basic detection of use-before-def and unresolved imports, and doesn't have the ability to disable checks per line (#264). What you can do in the meantime is disable the diagnostic in your settings, like:
"python.analysis.disabled": [ "use-before-def" ]
And use something like pylint which I don't believe will misreport this (with the downside that it can only be run on save, while the language server can do these checks instantly).
- changed the title
[-]Incorrect reporting of dataclass properties[/-][+]Use-before-def reported for class fields without default values[/+]on Nov 14, 2018 I have the same issue.
Jake Bailey (@jakebailey) there is a typo in
anaysis- it should be"python.analysis.disabled": [ "use-before-def" ]
Agh, yeah, sorry.
I hope these issues become a priority. VS code should really encourage the usage of the typing syntax!
Reacted by Farseen, James Hulse, oTree-org, Evren Özkan, SLAPaper Pang, Matías Iturburu, Wardy and N. Troy de FreitasThis was noticed on Stack Overflow.
Metadata
Metadata
Assignees
Labels
No labels
Environment data
VS Code version: 1.29.0
Extension version (available under the Extensions sidebar): 2018.10.1
OS and version: OSX
Python version (& distribution if applicable, e.g. Anaconda): python 3.7
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
Actual behavior
Python 3.7 dataclass properties are incorrectly reported as "used before definition". The same syntax with default values added is not reported.
Expected behavior
The properties are not reported.
Steps to reproduce:
See screenshot above.
BTW: is it possible (as a workaround to above issue) to suppress warnings for a given block/line?