[issue4220] Builtins treated as free variables?

2009-01-11 Thread Georg Brandl
Georg Brandl ge...@python.org added the comment: There is no way for the interpreter to distinguish between builtins and other types of free variables. If you need unqualified exec to work in an innner function, use function parameters with defaults, like this: def a(): def b(long=long):

[issue4220] Builtins treated as free variables?

2008-12-10 Thread Martin v. Löwis
Martin v. Löwis [EMAIL PROTECTED] added the comment: There is no proposed patch yet, so this is out of scope for 2.5.3. -- nosy: +loewis versions: -Python 2.5.3 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4220

[issue4220] Builtins treated as free variables?

2008-11-01 Thread Terry J. Reedy
Terry J. Reedy [EMAIL PROTECTED] added the comment: The request as stated is invalid. 'Int' and 'long' are built-in names, not keywords. The context of the cited sentence is If a name is bound in a block, it is a local variable of that block, unless declared as nonlocal. If a name is bound at

[issue4220] Builtins treated as free variables?

2008-11-01 Thread Terry J. Reedy
Changes by Terry J. Reedy [EMAIL PROTECTED]: -- versions: +Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4220 ___ ___ Python-bugs-list

[issue4220] Builtins treated as free variables?

2008-10-28 Thread David Fugate
New submission from David Fugate [EMAIL PROTECTED]: #-- VERSION AFFECTED: 2.5 and 2.6 BUILD TYPE: x86 FLAGS PASSED TO PYTHON.EXE: None OPERATING SYSTEM: 32-bit Windows Vista SP1

[issue4220] Builtins treated as free variables?

2008-10-28 Thread Alexander Belopolsky
Changes by Alexander Belopolsky [EMAIL PROTECTED]: -- nosy: +belopolsky ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4220 ___ ___ Python-bugs-list