Re: [Python-Dev] violently deprecating exec without in (was: nested scopes. global: have I got it right?)

...

...

...

...

"SP" == Samuele Pedroni writes:

SP> # top-level SP> def g(): SP> exec "x=3" SP> return x At the top-level, there is no closure created by the enclosing scope is not a function scope. I believe that's the right thing to do, except that the exec "x=3" also assign to the global. I'm not sure if there is a strong justification for allowing this form, except that it is the version of exec that is most likely to occur in legacy code. Jeremy