@ned-deily Just a few lines down from this change, the variable build_time_vars is used but it is unclear where that variable gets initiated. Could the # XXX this is extra-fragile comment be caused by an undefined variable?
./Mac/BuildScript/build-installer.py:1272:17: F821 undefined name 'build_time_vars'
for k, v in build_time_vars.items():
^
./Mac/BuildScript/build-installer.py:1543:50: F821 undefined name 'commandline'
raise RuntimeError("command failed: %s"%(commandline,))
^
E901,E999,F821,F822,F823 are the "showstopper" flake8 issues that can halt the runtime with a SyntaxError, NameError, etc. These 5 are different from most other flake8 issues which are merely "style violations" -- useful for readability but they do not effect runtime safety.
F821: undefined name name
F822: undefined name name in __all__
F823: local variable name referenced before assignment
E901: SyntaxError or IndentationError
E999: SyntaxError -- failed to compile a file into an Abstract Syntax Tree
This comment has been minimized.
cclauss commented onMay 1, 2019
9bdd6d1@ned-deily Just a few lines down from this change, the variable build_time_vars is used but it is unclear where that variable gets initiated. Could the # XXX this is extra-fragile comment be caused by an undefined variable?
flake8 testing of https://github.com/python/cpython on Python 3.7.1
$ flake8 . --count --select=E9,F63,F72,F82 --show-source --statistics
E901,E999,F821,F822,F823 are the "showstopper" flake8 issues that can halt the runtime with a SyntaxError, NameError, etc. These 5 are different from most other flake8 issues which are merely "style violations" -- useful for readability but they do not effect runtime safety.
namenamein__all__