Why not 3.__class__ ?  James_Althoff at i2.com James_Althoff at
i2.com Fri Oct 12 00:25:59 CEST 2001  Tim Peters wrote: >They're
supposed to be ugly:  if you find yourself using __xxx__
thingies >lot, it's supposed to be a clue that you're not using
the language as  Point taken.  (In his defense, he reminds the
jury that he *did* end his remark with a "full wink").  BTW,
I've just written a Jython-based debugger-type thingie that
provides a GUI in which you (our developers, that is) can
visually inspect all fields, methods, base classes, etc. for any
object (including Java instances, Python builtin objects, class
objects, etc.) in any of our applications (whilst it -- the
application -- is running).  Moreover you (the developer, again)
can change (using the GUI) any field value on the fly (or add or
delete same).  And, most importantly, you can rewrite a method
on the fly (using the GUI) -- restricted to Python methods, of
course, not for Java methods because Java is less dynamic and,
hence, quite inferior to