[issue5578] unqualified exec in class body

Changes by Terry J. Reedy : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue5578] unqualified exec in class body

Terry J. Reedy added the comment: Is there any currently relevant discrepancy between doc and behavior claimed in this issue. As far as I can see, the 2.7 docs for exec and def make no mention of exec being prohibited in def, let alone class statements. Ditto for exec() in 3.x. Anything earli

[issue5578] unqualified exec in class body

Jeremy Hylton added the comment: Why did it change from 2.5 to 2.6? I'm not sure that the change makes any sense. (Dreading the answer that I changed it...) -- ___ Python tracker _

[issue5578] unqualified exec in class body

Martin v. Löwis added the comment: Reopening. The following piece of code changed it behavior between 2.5 and 2.6: def f(): a = 2 class C: exec 'a = 42' abc = a return C print f().abc In 2.6, this returns 2, because static analysis determines that the read of 'a' comes from f'

[issue5578] unqualified exec in class body

Jeremy Hylton added the comment: exec is allowed in a class statement -- resolution: accepted -> rejected status: open -> closed ___ Python tracker ___ __

[issue5578] unqualified exec in class body

Changes by Jeremy Hylton : -- assignee: -> jhylton nosy: +jhylton resolution: -> accepted type: -> behavior ___ Python tracker ___ _

[issue5578] unqualified exec in class body

Amaury Forgeot d'Arc added the comment: Why should this code fail? I cannot see the problem you try to solve. -- nosy: +amaury.forgeotdarc ___ Python tracker ___

[issue5578] unqualified exec in class body

New submission from Maciek Fijalkowski : A patch and a test. The problem is a bit broader - what about import * etc? Patch fixes that, but without a test. -- components: Interpreter Core files: out.diff keywords: patch messages: 84259 nosy: fijal severity: normal status: open title: unq