[Python-checkins] python/dist/src/Doc/lib libprofile.tex, 1.48, 1.48.2.1

rhettinger at users.sourceforge.net rhettinger at users.sourceforge.net
Sun Dec 19 21:33:11 CET 2004


Update of /cvsroot/python/python/dist/src/Doc/lib
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv12142

Modified Files:
      Tag: release24-maint
	libprofile.tex 
Log Message:
Bug #1066607:  "Limitations" section of profiler docs is incorrect



Index: libprofile.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libprofile.tex,v
retrieving revision 1.48
retrieving revision 1.48.2.1
diff -u -d -r1.48 -r1.48.2.1
--- libprofile.tex	7 Nov 2004 06:18:37 -0000	1.48
+++ libprofile.tex	19 Dec 2004 20:33:08 -0000	1.48.2.1
@@ -536,16 +536,7 @@
 
 \section{Limitations \label{profile-limits}}
 
-There are two fundamental limitations on this profiler.  The first is
-that it relies on the Python interpreter to dispatch \dfn{call},
-\dfn{return}, and \dfn{exception} events.  Compiled \C{} code does not
-get interpreted, and hence is ``invisible'' to the profiler.  All time
-spent in \C{} code (including built-in functions) will be charged to the
-Python function that invoked the \C{} code.  If the \C{} code calls out
-to some native Python code, then those calls will be profiled
-properly.
-
-The second limitation has to do with accuracy of timing information.
+One limitation has to do with accuracy of timing information.
 There is a fundamental problem with deterministic profilers involving
 accuracy.  The most obvious restriction is that the underlying ``clock''
 is only ticking at a rate (typically) of about .001 seconds.  Hence no



More information about the Python-checkins mailing list