You often see people using the profiler for benchmarking instead of
profiling.  I suggest adding a note that explains that the profiler
modules are designed to provide an execution profile for a given
program, not for benchmarking different libraries or, even worse,
benchmarking Python code against C libraries.  Point people to the
"timeit" module if they want resonably accurate results.

(and yes, it would be nice if the copyright text on the page

http://docs.python.org/dev/library/profile.html

was moved to the bottom of the page.  If necessary, add something like
"This description of the profile module is Copyright © 1994, by InfoSeek
Corporation, all rights reserved.  Full copyright message below" at the
top.)

(the reason this is extra bad for C modules is that the profilers
introduce overhead for Python code, but not for C-level functions.  For
example, using the standard profiler to benchmark parser performance for
xml.etree.ElementTree vs. xml.etree.cElementTree will make ET appear to
be about 10 times slower than it actually is.)

Hello,
Here's a patch that implement what's request by Fredrik.

Regards,
Sandro

Freshed up and committed in r85451.