[issue34483] eval() raises NameError: name '...' is not defined

Eric V. Smith added the comment: I'll close this. I'm still reviewing the docs on it, and I might open a documentation issue once I understand it better. -- resolution: -> not a bug stage: -> resolved status: open -> closed type: -> behavior

[issue34483] eval() raises NameError: name '...' is not defined

Alex added the comment: Eric, thank you for the clarification. Do you want me to close the ticket? -- ___ Python tracker ___ ___

[issue34483] eval() raises NameError: name '...' is not defined

Change by Steven D'Aprano : -- nosy: +steven.daprano ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34483] eval() raises NameError: name '...' is not defined

Eric V. Smith added the comment: I believe you're seeing this: https://docs.python.org/3/reference/executionmodel.html#naming-and-binding See the paragraph that starts with "Class definition blocks and arguments to exec() and eval() are special in the context of name resolution", and the

[issue34483] eval() raises NameError: name '...' is not defined

New submission from Alex : Builtin eval() function raises NameError on a valid expression: --- example of bug on Python 3.4 Python 3.4.5 (default, May 29 2017, 15:17:55) [GCC 4.8.5 20150623 (Red Hat 4.8.5-11)] on linux Type "help", "copyright", "credits" or "license" for more information. >>>