summaryrefslogtreecommitdiffstats
path: root/Doc/lib/libprofile.tex
diff options
context:
space:
mode:
authorGuido van Rossum <guido@python.org>1997-11-18 15:28:46 (GMT)
committerGuido van Rossum <guido@python.org>1997-11-18 15:28:46 (GMT)
commit364e643fddf8a0365509033b2fd588ecbf84b7dc (patch)
treeb2e98521706e371e7dfe0a87e1251f1c2e6f64fb /Doc/lib/libprofile.tex
parent5de64883d8c28b0f294bc3ff5ef024d0da4aca86 (diff)
downloadcpython-364e643fddf8a0365509033b2fd588ecbf84b7dc.zip
cpython-364e643fddf8a0365509033b2fd588ecbf84b7dc.tar.gz
cpython-364e643fddf8a0365509033b2fd588ecbf84b7dc.tar.bz2
Clarified reference to old profiler.
Mention conversion to Perl-style regular expressions.
Diffstat (limited to 'Doc/lib/libprofile.tex')
-rw-r--r--Doc/lib/libprofile.tex10
1 files changed, 7 insertions, 3 deletions
diff --git a/Doc/lib/libprofile.tex b/Doc/lib/libprofile.tex
index 2f69170..52156a3 100644
--- a/Doc/lib/libprofile.tex
+++ b/Doc/lib/libprofile.tex
@@ -57,6 +57,9 @@ examine the results of a profile operation.
\section{How Is This Profiler Different From The Old Profiler?}
\nodename{Profiler Changes}
+(This section is of historical importance only; the old profiler
+discussed here was last seen in Python 1.1.)
+
The big changes from old profiling module are that you get more
information, and you pay less CPU time. It's not a trade-off, it's a
trade-up.
@@ -441,9 +444,10 @@ the significant entries. Initially, the list is taken to be the
complete set of profiled functions. Each restriction is either an
integer (to select a count of lines), or a decimal fraction between
0.0 and 1.0 inclusive (to select a percentage of lines), or a regular
-expression (to pattern match the standard name that is printed). If
-several restrictions are provided, then they are applied sequentially.
-For example:
+expression (to pattern match the standard name that is printed; as of
+Python 1.5b1, this uses the Perl-style regular expression syntax
+defined by the \code{re} module). If several restrictions are
+provided, then they are applied sequentially. For example:
\bcode\begin{verbatim}
print_stats(.1, "foo:")