The Profile class of module profile was
written so that derived classes could be developed to extend the profiler. The details are not
described here, as doing this successfully requires an expert understanding of how the Profile class works internally. Study the source code of module profile carefully if you want to pursue this.
If all you want to do is change how current time is determined (for example, to force use
of wall-clock time or elapsed process time), pass the timing function you want to the Profile class constructor:
pr = profile.Profile(your_time_func)
The resulting profiler will then call
your_time_func(). The function should
return a single number, or a list of numbers whose sum is the current time (like what os.times() returns). If the function returns a single time number, or
the list of returned numbers has length 2, then you will get an especially fast version of the
Be warned that you should calibrate the profiler class for the timer function that you
choose. For most machines, a timer that returns a lone integer value will provide the best
results in terms of low overhead during profiling. (os.times() is pretty
bad, as it returns a tuple of floating point values). If you want to substitute a better timer
in the cleanest fashion, derive a class and hardwire a replacement dispatch method that best
handles your timer call, along with the appropriate calibration constant.