[Python-Dev] trace.py and the obscurity of Tools/scripts/ (was: Unittest list) (original) (raw)

Kevin Jacobs jacobs@penguin.theopalgroup.com
Fri, 12 Apr 2002 22:15:48 -0400 (EDT)

On Fri, 12 Apr 2002, Skip Montanaro wrote:

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

Jeremy> Can any of the handler methods be re-coded in C? The hotshot Jeremy> changes allow you to install a C function as a trace hook, but Jeremy> doesn't the trace function in trace.py do a fair amount of work? Dunno. As you might guess I haven't looked at the trace code in quite awhile... :-)

One way to make the function tracking code faster is to use the profiler hooks instead of the tracer hooks. I've already made this and many othe rcleanups nad bug fixes on my local version. I'm also looking at translating bits into C, though I've been side-tracked by an import related problem that trashes module paths.

-Kevin

-- Kevin Jacobs The OPAL Group - Enterprise Systems Architect Voice: (216) 986-0710 x 19 E-mail: jacobs@theopalgroup.com Fax: (216) 986-0714 WWW: http://www.theopalgroup.com