Getting a class name

[Harlin Seritt]

Hi,

How does one get the name of a class from within the class code? I
tried something like this as a guess:

self.__name__

Obviously it didn't work.

Anyone know how to do that?

Thanks,

Harlin

[Bruno Desthuilliers]

Gabriel Genellina a écrit :

En Sun, 18 Feb 2007 14:14:41 -0300, goodwolf <Ro**********@g mail.com>
escribió:

>On Feb 18, 9:17 am, "Gabriel Genellina" <gagsl...@yahoo .com.arwrote:

>>En Sun, 18 Feb 2007 04:20:33 -0300, goodwolf <Robert.Ka...@g mail.com>
escribió:

I suppose that you wont get class name into its code (or before
definition end) but not into a method definition.

import sys

def getCodeName(dea p=0):
return sys._getframe(d eap+1).f_code.c o_name

class MyClass (object):
name = getCodeName() + '!'

What's the advantage over MyClass.__name_ _?

--
Gabriel Genellina

>>>>class C(object):

... name = C.__name__
...
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "<stdin>", line 2, in C
NameError: name 'C' is not defined

>>>>>

I were asking, why do you want a "name" attribute since "__name__"
already exists and has the needed information. And worst, using an
internal implementation function to do such task.

This might be useful to avoid metaclass hacks when trying to initialize
a class attribute that would require the class name. (my 2 cents)

[Fuzzyman]

On Feb 18, 11:54 pm, Bruno Desthuilliers
<bdesth.quelque [e-mail] quepart.frwrote :

Gabriel Genellina a écrit :

En Sun, 18 Feb 2007 14:14:41 -0300, goodwolf <Robert.Ka...@g mail.com>
escribió:

On Feb 18, 9:17 am, "Gabriel Genellina" <gagsl...@yahoo .com.arwrote:

>En Sun, 18 Feb 2007 04:20:33 -0300, goodwolf <Robert.Ka...@g mail.com>
escribió:

I suppose that you wont get class name into its code (or before
definition end) but not into a method definition.

import sys

def getCodeName(dea p=0):
return sys._getframe(d eap+1).f_code.c o_name

class MyClass (object):
name = getCodeName() + '!'

>What's the advantage over MyClass.__name_ _?

>--
Gabriel Genellina

>>>class C(object):

... name = C.__name__
...
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "<stdin>", line 2, in C
NameError: name 'C' is not defined

I were asking, why do you want a "name" attribute since "__name__"
already exists and has the needed information. And worst, using an
internal implementation function to do such task.

This might be useful to avoid metaclass hacks when trying to initialize
a class attribute that would require the class name. (my 2 cents)

It's still an ugly hack. :-)

(But a nice implementation detail to know about none-the-less.)

Fuzzyman
http://www.voidspace.org.uk/python/articles.shtml

[Gabriel Genellina]

En Sun, 18 Feb 2007 20:56:48 -0300, Fuzzyman <fu******@gmail .comescribió:

[somebody] wrote:

>def getCodeName(dea p=0):
return sys._getframe(d eap+1).f_code.c o_name

>class MyClass (object):
name = getCodeName() + '!'

>>What's the advantage over MyClass.__name_ _?
I were asking, why do you want a "name" attribute since "__name__"
already exists and has the needed information. And worst, using an
internal implementation function to do such task.

This might be useful to avoid metaclass hacks when trying to initialize
a class attribute that would require the class name. (my 2 cents)

It's still an ugly hack. :-)
(But a nice implementation detail to know about none-the-less.)

Having class decorators would be nice...

--
Gabriel Genellina

[Fuzzyman]

On Feb 19, 5:11 am, "Gabriel Genellina" <gagsl...@yahoo .com.arwrote:

En Sun, 18 Feb 2007 20:56:48 -0300, Fuzzyman <fuzzy...@gmail .comescribió:

[somebody] wrote:

def getCodeName(dea p=0):
return sys._getframe(d eap+1).f_code.c o_name

class MyClass (object):
name = getCodeName() + '!'

>What's the advantage over MyClass.__name_ _?
I were asking, why do you want a "name" attribute since "__name__"
already exists and has the needed information. And worst, using an
internal implementation function to do such task.

This might be useful to avoid metaclass hacks when trying to initialize
a class attribute that would require the class name. (my 2 cents)

It's still an ugly hack. :-)
(But a nice implementation detail to know about none-the-less.)

Having class decorators would be nice...

Yes - and Guido said he wouldn't be opposed to the idea when it was
poitned out that they would be very useful for both IronPython and
Jython to implement features of their underlying platforms.

I haven't heard anyone (other than you) mention them recently
though...

Fuzzyman
http://www.voidspace.org.uk/python/articles.shtml

--
Gabriel Genellina

[Gabriel Genellina]

En Mon, 19 Feb 2007 17:25:56 -0300, Fuzzyman <fu******@gmail .comescribió:

On Feb 19, 5:11 am, "Gabriel Genellina" <gagsl...@yahoo .com.arwrote:

>En Sun, 18 Feb 2007 20:56:48 -0300, Fuzzyman <fuzzy...@gmail .com>
escribió:

[somebody] wrote:
def getCodeName(dea p=0):
return sys._getframe(d eap+1).f_code.c o_name

>This might be useful to avoid metaclass hacks when trying to

initialize

>a class attribute that would require the class name. (my 2 cents)

It's still an ugly hack. :-)
(But a nice implementation detail to know about none-the-less.)

Having class decorators would be nice...

Yes - and Guido said he wouldn't be opposed to the idea when it was
poitned out that they would be very useful for both IronPython and
Jython to implement features of their underlying platforms.

I haven't heard anyone (other than you) mention them recently
though...

Maybe it's a sign that actually nobody cares about class decorators :(

--
Gabriel Genellina