On Tue, 15 Mar 2005 [EMAIL PROTECTED] wrote:
> hi Danny, I had no idea Debian split its profiler into a separate
> package in the testing distro. That would explain it, except I am using
> Debian unstable with Debian stable for security packages, as my "more
> /etc/apt/sources.list" output is:
hi Danny, I had no idea Debian split its profiler into a separate package
in the testing distro. That would explain it, except I am using Debian
unstable with Debian stable for security packages, as my
"more /etc/apt/sources.list" output is:
nike:# more /etc/apt/sources.list
#deb file:///cdrom/
> This is highly unusual! This should have worked without any error
> messages, as both the 'profile' and 'hotshot' modules are part of the
> Standard Library, and should work out of the box.
Hi Tpc,
Oh, wait. The above statement is usually true, unless we're running
something from a Linux dis
On Tue, 15 Mar 2005 [EMAIL PROTECTED] wrote:
> So I tried using the example code verbatim to see if I get the same
> error messages, and I do! When I try "import hotshot.stats" I get:
>
> >>> import hotshot.stats
>
> Traceback (most recent call last):
> File "", line 1, in -toplevel-
> im
hi everyone, to anyone who has profiled their Python code using hotshot; I
designed a test case using hotshot that is basically a stripped down
version of the example code found here:
http://www.python.org/doc/current/lib/hotshot-example.html
So I tried using the example code verbatim to see if I
