[issue41392] SyntaxError rather than NameError

Eric V. Smith added the comment: As an example of why it's not possible for the compiler to treat this as a syntax error: I use python for my config files. Before I load these files, I inject names into the builtins, so that the config files can reference them. Some of these are constants, o

[issue41392] SyntaxError rather than NameError

Ronald Oussoren added the comment: The compiler cannot know if "false" is an existing name when compiling. One example is that the name might refer to the name of a builtin. -- nosy: +ronaldoussoren resolution: -> not a bug stage: -> resolved status: open -> closed type: compile er

[issue41392] SyntaxError rather than NameError

Change by wyz23x2 : -- title: SyntaxError rather than NameError error -> SyntaxError rather than NameError ___ Python tracker ___ _

[issue41392] SyntaxError rather than NameError error

wyz23x2 added the comment: There is nothing *wrong* with the syntax; it's just a regular assignment. It's not something like `False = 4` or `while = 6` which '=' is invalid. -- nosy: +wyz23x2 title: Syntax error rather than run time error -> SyntaxError rather than NameError error __