[Python-Dev] variable name resolution in exec is incorrect

[Michael Foord]

On 27/05/2010 00:38, Greg Ewing wrote:
> Mark Dickinson wrote:
>
>>>>> code = """\
>>
>> ... y = 3
>> ... def f():
>> ... return y
>> ... f()
>> ... """
>>
>>>>> exec code in {} # works fine
>>>>> exec code in {}, {} # dies with a NameError
>
> Seems to me the whole idea of being able to specify
> separate global and local scopes for top-level code is
> screwy in the first place. Are there any use cases for
> it? Maybe the second scope argument to exec() should
> be deprecated?
>
Sounds good to me, certainly ends the confusion over this undoubtedly 
unintuitive behaviour. :-)

Michael


-- 
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.