[Python-Dev] s/hotshot/lsprof

[Brett Cannon]

On 11/21/05, Jeremy Hylton <jeremy at alum.mit.edu> wrote:
> Here's another attempt to disentagle some issues:
> - Should lsprof be added to the standard distribution?
> - Should hotshot be removed from the standard distribution?
>
> These two aren't at all related, unless you believe that two is the
> maximum number of profiles allowed per Python distribution.
>

They aren't related if Hotshot provides some functionality that lsprof
cannot provide (such as profiling C code; I thought Nick Bastin added
support for this?).  But if there isn't, then there is some soft
relatedness between them since it means that if lsprof is added then
hotshot could be removed without backwards-compatibilty issues.  They
are not mutually exclusive, but one being true does influence the
other.

And as for how many profilers to have, I personally think one is
plenty if they all provide similar type of output using similar
techniques.  But backwards-compatibility obviously is going to make
total removal of a module and its API hard so I am thinking more
towards Python 3000 and having the best solution in now.  Otherwise we
should do what must be  done to fix hotshot and stick with it.

-Brett