[issue991196] An inconsistency with nested scopes

Mark Dickinson added the comment: > I'm guessing that somewhere in the python source there is some code that goes > [...] Unfortunately it's not nearly that simple. As I mentioned in my message on python-dev, the problem is that 'y' gets bound with a 'STORE_NAME' opcode, which puts 'y' into

[issue991196] An inconsistency with nested scopes

Changes by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue991196] An inconsistency with nested scopes

Colin Hawkett added the comment: #8819 was closed as duplicate. That issue linked a description of the problem on stack overflow http://stackoverflow.com/questions/2904274/globals-and-locals-in-python-exec. I would like to argue that this is a bug, and should be fixed in 2.6+. The definition

[issue991196] An inconsistency with nested scopes

Jeremy Hylton added the comment: This code behaves as intended. The module-level execution environment is different than other environments. The global scope and local scope are the same dictionary. Assignments at the top-level become globals because of this behavior of the execution environm

[issue991196] An inconsistency with nested scopes

Changes by Jeremy Hylton : -- assignee: -> jhylton nosy: +jhylton ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue991196] An inconsistency with nested scopes

Daniel Diniz added the comment: Confirmed in trunk, -- nosy: +ajaksu2 type: -> behavior versions: +Python 2.6 -Python 2.3 ___ Python tracker ___ __