[issue8819] variable resolution within exec() incorrect

Mark Dickinson added the comment: Hmm. To get this changed in 2.x you'd have to convince people that it really is a bug. You probably also need to do that very soon for there to be any hope of 2.7 having changed behaviour. I'd suggest bringing this up on the python-dev mailing list; it'll

[issue8819] variable resolution within exec() incorrect

Colin Hawkett added the comment: Apologies for raising it in the tracker against your advice. My thinking was that you were suggesting discussions about 3.x content shouldn't be in the tracker, and I wanted to argue that it is a bug and should be fixed in 2.6+ --

[issue8819] variable resolution within exec() incorrect

Colin Hawkett added the comment: Agreed, this is the same issue. I'll make my argument that this is a bug (intentional or otherwise) on that issue. -- ___ Python tracker ___ ___

[issue8819] variable resolution within exec() incorrect

Mark Dickinson added the comment: Judging by the issue 991196 discussion, the described behaviour is intentional. In particular, this behaviour isn't likely to change in Python 2.x: 2.6 is in bugfix only mode, and 2.7 is too close to release to start messing with internals. You may be able

[issue8819] variable resolution within exec() incorrect

Mark Dickinson added the comment: This looks like a duplicate of issue 991196. -- nosy: +mark.dickinson ___ Python tracker ___ ___ Pyt

[issue8819] variable resolution within exec() incorrect

New submission from Colin Hawkett : A discussion on stack overflow - http://stackoverflow.com/questions/2904274/globals-and-locals-in-python-exec - has led to the conclusion that the variable lookup behaviour within code run using exec() is not behaving as expected. Variable lookup inside a cl