what does "execfile" mean within profiler output and why does it not have a attached line number

Rahul nospam at nospam.invalid
Sun Apr 5 01:56:51 CEST 2009


"profile" tells me that most of my runtime was spent in just one part (1.28 
sec cumulatively out of 1.29 secs. But what is "execfile"? I don't see this 
as a function call with my python code. Also what's the 0 in the snippet:  
":0(execfile)"? Isn't there supposed to be a line-number? 

Looking up "execfile" in the python manual leads me to "exec": "This 
statement supports dynamic execution of Python code."

But that seems pretty generic; how can I now try figuring out which part of 
my python file is the bottleneck? 

Sorry, I'm a newbiee to profiling.


######################################################################
       51651 function calls (37762 primitive calls) in 1.290 CPU seconds
 ncalls  tottime  percall  cumtime  percall filename:lineno(function)
[snip]
    1    0.010    0.010    1.280    1.280 :0(execfile)
[snip]
##########################################################




-- 
Rahul



More information about the Python-list mailing list