Author xiaq
Recipients georg.brandl, gvanrossum, xiaq
Date 2012-07-29.15:22:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1343575347.26.0.517885081261.issue633930@psf.upfronthosting.co.za>
In-reply-to
Content
There is a bigger problem:

>>> class C:
...     class D:
...         pass
...
>>> repr(C)
"<class '__main__.C'>"
>>> repr(C.D)
"<class '__main__.D'>"

Default repr on nested classes produce specious results.

The problem become pratical when you have two nested classes C1.D and C2.D in module m, which end up being both "m.D" in exception traceback. 

Classes nested in function are likely to contain some information from the function arguments and are thus different on each function call, making it impossible to have a general way to name them. Thus I propose embedding the resulting class's `id` in __name__, like what i'm doing manually in a hulking way:

>>> def factory(foo):
...     class C(object):
...         bar = foo
...     func_name = 'factory'
...     C.__name__ = '%s generated classobj at 0x%x' % (func_name, id(C))
...     return C
...
>>> factory(0)
<class '__main__.factory generated classobj at 0x32273c0'>
>>> factory(0)
<class '__main__.factory generated classobj at 0x32245b0'>

Please consider reopening this issue.
History
Date User Action Args
2012-07-29 15:22:27xiaqsetrecipients: + xiaq, gvanrossum, georg.brandl
2012-07-29 15:22:27xiaqsetmessageid: <1343575347.26.0.517885081261.issue633930@psf.upfronthosting.co.za>
2012-07-29 15:22:26xiaqlinkissue633930 messages
2012-07-29 15:22:26xiaqcreate