Python 2.2a1 (#1, Jul 19 2001, 18:18:51)
[GCC 2.96 20000731 (Red Hat Linux 7.1 2.96-81)] on 
linux2

The intepreter dies hard if you directly evaluate the 
func_code of a function that has a closure. E.g.:

-----
def func1():
    return lambda: 4 + y

f = func1()
print "Ugly test 1:", eval( f.func_code, {'y': 38} )


def func2(x):
    return lambda: x + y

f = func2(4)
print "Ugly test 2:", eval( f.func_code, {'y': 38} )
-----

The second eval will cause a core dump on UNIX. The 
offending code is in PyEval_EvalCodeEx() of ceval.c 
line 2466. This loop attempts to match free vars 
against the closure, but the closure is NULL if the 
function is called with eval.

I know this is very broken usage of the interpreter, 
but it should die more cleanly than a core dump ;-)

Logged In: YES 
user_id=31435

Assigned to Jeremy in the hopes this will speed his return 
to us <wink>.

Logged In: YES 
user_id=31392

Fixed in rev 2.219 of bltinmodule.c

Logged In: YES 
user_id=31392

It might be useful to extend eval() with a means to specify
bindings from free variables.  It's not at all clear how to
do this under the current implementation, which refers to
free variables using integer indexes assigned at compile
time.

Logged In: YES 
user_id=6380

Jeremy, since you claimed this to be fixed, is there a
reason to keep this bug report open? If you want a feature,
please open a (new, please!) feature request.

Logged In: YES 
user_id=44345

just a reminder that this appears to be fixed -skip

Logged In: YES 
user_id=31392

Added feature request to pep 42.