Question

When I look at the dictionary generated with:

import trace
tracer = trace.Trace(countfuncs=True)
tracer.runfunc(callableObj, *args, **kwargs)
print tracer.results().calledfuncs

on one machine (python 1.3) I get a strange syntax for the keys of the printed dictionary; a key looks like:

('/path/to/file.py', 'module', "SomeClass'>.some_method")

The thing I wonder about are the characters: ‘>

On another machine with python 1.3.1 the third tuple-entry looks like expected, without the ‘> bit.

Have you got an idea where this comes from and why its there on one machine and not on another?

Answer 1

Are you sure you didn’t mean Python 2.3?

In trace.py, the classname is calculated from:

    ...
        clsname = str(classes[0])
    ...
    if clsname is not None:
        # final hack - module name shows up in str(cls), but we've already
        # computed module name, so remove it
        clsname = clsname.split(".")[1:]
        clsname = ".".join(clsname)
        funcname = "%s.%s" % (clsname, funcname)

Usually str(someclass) gives you something like module.klass so splitting at the dot gives you a clean name for the class. For some reason the class on the system you are looking at is giving a repr that ends with the string you are seeing, so perhaps it was something like <proxy for 'module.klass'>.

I would try editing trace.py on that machine to (temporarily) not split the clsname variable and then you might be able to figure out what it should really say.