[Python-Dev] trace.py and the obscurity of Tools/scripts/

Fred L. Drake, Jr. fdrake@acm.org
Thu, 6 Jun 2002 15:12:36 -0400

[cleaning out some old mail...]

Zooko wrote:
 > So in terms of `trace.py', it is a widely useful tool and
 > already has a programmatic interface.  Being added to the
 > hallowed Python Standard Library would be a major step up in
 > publicity and hence usage.  It would require better docs
 > regarding the programmatic usage.

Skip wrote:
 > It's speed cries out for a rewrite of some sort.  I haven't
 > thought about it, but I wonder if it could be layered on top of
 > hotshot.

Jeremy Hylton writes:
 > Can any of the handler methods be re-coded in C?  The hotshot changes
 > allow you to install a C function as a trace hook, but doesn't the
 > trace function in trace.py do a fair amount of work?

Another possibility is to use _hotshot.coverage() instead of the
"normal" profiler in HotShot.  This records the enter/exit events and
SET_LINENO instructions, but doesn't take any timing measurements, so
operates much quicker than profiling.


Fred L. Drake, Jr.  <fdrake at acm.org>
PythonLabs at Zope Corporation