In the test suite for one of my packages, I've used
something like gen.gi_frame.f_code.co_name to help make
human-readable assertions about when certain generators
are run deep inside the application. This was possible
because Python 2.4 guaranteed that gi_frame was always
a frame instance, even after the generator exhausted
itself. In Python 2.5, however, gi_frame is None when
the generator has run till exhaustion, meaning that I
can't always get to f_code.co_name.

I'd like to add a gi_code attribute to generators that
would allow users to access the code object behind the
generator, even when gi_frame is None. This attribute
would be read-only and would follow this rule:

>>> def f():
...     yield 5
...
>>> g = f()
>>> g.gi_code is f.func_code
True
>>>

The attached patch (against r45570) implements the
proposed attribute (in Include/genobject.h and
Objects/genobject.c) and adds test cases to
Lib/test/test_generators.py for this attribute.

Logged In: YES 
user_id=1344176

I've updated the patch; it's now against SVN r45808.

Logged In: YES 
user_id=849994

Phillip, do you have an opinion on this one?

Logged In: YES 
user_id=1344176

In addition to updating the main patch to r46040, I've
included a diff against Misc/NEWS to make mention of the
gi_code attribute.

Any thoughts on getting this into 2.5a3?

Guido, do you have an opinion? Seems like a nonproblematic and probably
useful change for 2.6.

I noticed some whitespace issues in the patch, but apart from that I
have no objection.  (Not any particular enthusiasm, I have to admit -- I
don't quite get the use case, but as Georg remarks, it seems harmless.)

Reformatted the patch to use tabs and committed as r60324.