Metaclass mystery

LittleGrasshopper seattlehanks at
Mon Jun 1 19:08:50 CEST 2009

On Jun 1, 12:18 am, Lie Ryan <lie.1... at> wrote:
> LittleGrasshopper wrote:
> > On May 31, 2:03 pm, a... at (Aahz) wrote:
> >> In article <eaf75582-0d22-4b31-b0e7-b8e5baa5c... at>,
> >> LittleGrasshopper  <seattleha... at> wrote:
> >>>> On May 31, 12:19=A0am, Arnaud Delobelle <arno... at> wrote:
> >>>>> [1]
> >>> 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.
> >>> Is this stuff actually tough, or am I just a dummy?
> >> Definitely tough!  Metaclasses can cause dain bramage.
> >> --
> >> Aahz (a... at           <*>
> >> my-python-code-runs-5x-faster-this-month-thanks-to-dumping-$2K-
> >>     on-a-new-machine-ly y'rs  - tim
> > Good to know, I'll stick to it and persevere. Will check doctor
> > regularly for dain bramage though.
> Fortunately python makes it rare that we actually need to use metaclass.
> Especially with class decorators and such...
> With that said, the rare cases where it is really needed; brain
> hemorrhage is not only possible but when.


I understand what you mean about metaclasses not being something that
everybody needs to master on an everyday basis. Unfortunately, I'm the
type of person that has to know how things work. I consider this an
unfortunate defect, due to the fact that I am unable to compromise and
let go even when practical considerations would dictate that is the
appropriate course of action.

I'm going to stick with this. I haven't even read the official
Reference manual, so maybe I'm getting ahead of myself though. My
plans are to read the reference manual, then selected parts of the
library manual, and take it from there.

More information about the Python-list mailing list