Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <b8a1c0cb-a52e-466b-af2a-64059f4e8be3@googlegroups.com>
References: <b8a1c0cb-a52e-466b-af2a-64059f4e8be3@googlegroups.com>
From: Ian Kelly <ian.g.kelly@gmail.com>
Date: Mon, 18 Nov 2013 13:43:28 -0700
Subject: Re: Why do only callable objects get a __name__?
To: Python <python-list@python.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.2862.1384807451.18130.python-list@python.org>
Lines: 70
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:59906

On Mon, Nov 18, 2013 at 1:13 PM, John Ladasky
<john_ladasky@sbcglobal.net> wrote:
> A few days ago, I asked about getting the original declared name of a fun=
ction or method, and learned about the __name__ attribute.
>
> https://groups.google.com/forum/#!topic/comp.lang.python/bHvcuXgvdfA
>
> Of course, I have used __name__ for years in the common expression "if __=
name__ =3D=3D "__main__") to determine whether a particular module is being=
 run or merely imported.  But until recently, I never went deeper than that=
.
>
> I just created an object using collections.namedtuple, and was surprised =
to discover that it didn't have a __name__ -- even though something that be=
haves like __name__ is clearly accessible and printable.  Here's some minim=
al Python 3.3.2 code and output:
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> from collections import namedtuple
>
> MyNamedTupleClass =3D namedtuple("ANamedTuple", ("foo", "bar"))
> nt =3D MyNamedTupleClass(1,2)
> print(nt)
> print(type(nt))
> # print(nt.__name__) # this would raise an AttributeError
> print(type(nt).__name__) # this is the desired output
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> ANamedTuple(foo=3D1, bar=3D2)
> <class '__main__.ANamedTuple'>
> ANamedTuple
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> As you can see, I snooped around in the object's type.  I found that the =
type, rather than the object itself, had the __name__ I was seeking.  I the=
n read the Python docs concerning __name__ and found that this attribute is=
 restricted to callable objects.
>
> This leads me to ask two questions:
>
> 1. WHY do only callable objects get a __name__?  A __name__ would seem to=
 be a useful feature for other types.  Clearly, whoever implemented namedtu=
ple thought it was useful to retain and display that information as a part =
of the string representation of the namedtuple (and I agree).

Classes and functions are frequently kept in module namespaces, where
they are known by a specific name.  The intent is that the __name__
attribute should match that name by which it is commonly referred.

Specific instances are not typically widely referred to by set names
in this way.  They are more commonly stored in variables that are used
to hold a wide variety of objects.

In the namedtuple example that you give, it seems that you would want
the names of all instances of the ANamedTuple class to be the same
"ANamedTuple", and I really don't see what the purpose of giving them
all the same name would be.

> 2. If I created a superclass of namedtuple which exposed type(namedtuple)=
.__name__ in the namespace of the namedtuple itself, would I be doing anyth=
ing harmful?

Probably not.  But why not just invent your own name attribute rather
than shadow the one that Python designates for classes and functions?