profiler results for __getattr__, am I reading this correctly ?

[Tim Peters]

[Tim]
> Try grabbing profile.py out of the current CVS tree (it should run fine
> under 2.1.1 too, and under 2.0.1).  There was a systematic bug ...

[Neil Schemenauer]
> I've ran into this problem just the other day and using profile.py out
> of CVS fixed it for me.

I believe it:  this is yet another instance of the simultaneous worldwide
discovery of a bug that always existed!  Not just you, but also someone on
SourceForge, and what got it bumped to the top of the list is that several
coworkers in Zope Corp were being driven insane by it.  Guido, Fred and I
each spent (overall) most of a workday going over every line in profile.py
with hyper-critical eyes, and we believe the bug is well and truly squashed.
Plus, in 2.2, we no longer generate the screwy profiling events that were
confusing it to begin with.

> Hmm, 2.1.2?

If volunteers materialize to produce another bugfix release, I'm sure we'll
(PythonLabs) be happy to ship it (cut docs, installers, etc).  It's curious
that neither Aahz (2.0.1) nor Thomas Wouters (2.1.1) volunteered for a
second round of this rewarding work <wink>.