Nested class __name__ #37422

Activity

1. gvanrossum commented on Nov 5, 2002

   

   gvanrossum

   on Nov 5, 2002

   MemberAuthor

   More actions

   The __name__ attribute of a nested class should be set
   to 'outer.inner', both for classic and for new-style
   classes. E.g.

   >>> class C:
   ...     class C1: pass
   ... 
   >>> C.C1.__name__
   'C.C1'
   >>>
2. gvanrossum

   closed this as completedon Nov 5, 2002
3. gvanrossum

   self-assigned this

   on Nov 5, 2002
4. gvanrossum

   added

   interpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)

   on Nov 5, 2002
5. gvanrossum

   closed this as completedon Nov 5, 2002
6. gvanrossum

   self-assigned this

   on Nov 5, 2002
7. gvanrossum

   added

   interpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)

   on Nov 5, 2002
8. gvanrossum commented on Nov 14, 2002

   

   gvanrossum

   on Nov 14, 2002

   MemberAuthor

   More actions

   Logged In: YES
   user_id=6380

   Hm, but should this also be done for functions inside
   classes? E.g.

   class C:
    def foo(self): pass

   assert C.foo.__name__ == "C.foo"
   assert C.__dict__["foo"].__name__ == "C.foo"

   And what about classes inside functions?

   def f():
     class C: pass
     return C

   assert f().__name__ == "f.C"

   ???
9. gvanrossum commented on Feb 11, 2003

   

   gvanrossum

   on Feb 11, 2003

   MemberAuthor

   More actions

   Logged In: YES
   user_id=6380

   I'm less sure I even want this now, and not at all sure how
   to do it any more, so lowering priority.
10. birkenfeld commented on Mar 10, 2007

    

    birkenfeld

    on Mar 10, 2007

    Member

    More actions

    Any interest for Python 3000 on this? Otherwise we can close it.
11. gvanrossum commented on Mar 10, 2007

    

    gvanrossum

    on Mar 10, 2007

    MemberAuthor

    More actions

    I don't think so. Closing.
12. xiaq commented on Jul 29, 2012

    

    xiaqmannequin

    on Jul 29, 2012

    Mannequin

    More actions

    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.
13. mstefanro commented on Jul 29, 2012

    

    mstefanromannequin

    on Jul 29, 2012

    Mannequin

    More actions

    Only an issue in Python2.

        >>> A.B.__qualname__
        'A.B'
        >>> repr(A.B)
        "<class '__main__.A.B'>"
14. ezio-melotti

    transferred this issue fromon Apr 9, 2022