Metaclass mystery

[LittleGrasshopper]

On May 31, 9:24 am, LittleGrasshopper <seattleha... at yahoo.com> wrote:
> On May 31, 12:19 am, Arnaud Delobelle <arno... at googlemail.com> wrote:
>
>
>
> > LittleGrasshopper <seattleha... at yahoo.com> writes:
> > > On May 30, 6:15 pm, Carl Banks <pavlovevide... at gmail.com> wrote:
> > >> On May 30, 5:32 pm, LittleGrasshopper <seattleha... at yahoo.com> wrote:
>
> > >> > On May 30, 4:01 pm, LittleGrasshopper <seattleha... at yahoo.com> wrote:
>
> > >> > > I am experimenting with metaclasses, trying to figure out how things
> > >> > > are put together.
>
> > Have you read Guido's 'Unifying types and classes in Python 2.2' [1]?  I
> > read it a long time ago but I remember it being very enlightening.
>
> > [1]http://www.python.org/download/releases/2.2.3/descrintro/
>
> > --
> > Arnaud
>
> I haven't actually read it, but I will now. Thanks for pointing it
> out, Arnaud.

I'm about 2/3 of the way through this paper (although I don't claim to
understand all of it.) There is some heavy duty material in there,
enough to make me feel really stupid and frustrated at times. I'm
making connections as I go though, hopefully everything will sink in
eventually.

The discussion on super(), especially the python code implementation,
clarified some of the doubts I had about how it is implemented
(including "unbound" super objects, which involve the descriptor
mechanism on the super object itself.)

Is this stuff actually tough, or am I just a dummy?