Bug #24792
Fix pylint errors as of 8/14
Start date:
08/14/2020
Due date:
% Done:
0%
Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Description
Continue pylint cleanup
History
#1 Updated by Thomas Hein 5 months ago
Pylint error below is addressed in branch v3p3/24792_2
- Module lib.exprParser
lib/exprParser.py:15:0: E0401: Unable to import 'compiler' (import-error)
lib/exprParser.py:18:0: E0401: Unable to import 'compiler.ast' (import-error)
#2 Updated by Thomas Hein 5 months ago
PyLint triggers an undefined-all-variable exception for init.py which contains
all=["factory", "frontend", "lib", "tools", "creation", "install", "unittests"]
Error generated from the PyLint test,
- Module unittests.test_lib_fork
unittests/test_lib_fork.py:168:8: E1111: Assigning result of a function call, where the function has no return (assignment-from-no-return) - Module init
init.py:1:9: E0603: Undefined variable name 'factory' in all (undefined-all-variable)
init.py:1:20: E0603: Undefined variable name 'frontend' in all (undefined-all-variable)
init.py:1:32: E0603: Undefined variable name 'lib' in all (undefined-all-variable)
init.py:1:39: E0603: Undefined variable name 'tools' in all (undefined-all-variable)
init.py:1:48: E0603: Undefined variable name 'creation' in all (undefined-all-variable)
init.py:1:60: E0603: Undefined variable name 'install' in all (undefined-all-variable)
init.py:1:71: E0603: Undefined variable name 'unittests' in all (undefined-all-variable)
A valid fix might be,
all = ["factory", "frontend", "lib", "tools", "creation", "install",
"unittests"] # pylint: disable=undefined-variable
But is the PyLint test misconfigured or should the above be used to address this issue?
#3 Updated by Marco Mambelli 4 months ago
- Target version changed from 2122 to v3_9_1