summaryrefslogtreecommitdiffstats
path: root/Doc/lib
diff options
context:
space:
mode:
authorFred Drake <fdrake@acm.org>2004-03-23 20:30:59 (GMT)
committerFred Drake <fdrake@acm.org>2004-03-23 20:30:59 (GMT)
commite05c3e0fbbec3edb242da330601c5725d28e3a4e (patch)
treec3ebe56cb02ca00cddf0632158e7f9ca159767c2 /Doc/lib
parent4ac6c6afc347cea41b879355672b081c907dc1ed (diff)
downloadcpython-e05c3e0fbbec3edb242da330601c5725d28e3a4e.zip
cpython-e05c3e0fbbec3edb242da330601c5725d28e3a4e.tar.gz
cpython-e05c3e0fbbec3edb242da330601c5725d28e3a4e.tar.bz2
fix markup nits
Diffstat (limited to 'Doc/lib')
-rw-r--r--Doc/lib/libprofile.tex8
1 files changed, 4 insertions, 4 deletions
diff --git a/Doc/lib/libprofile.tex b/Doc/lib/libprofile.tex
index fa0f6b3..50db92e 100644
--- a/Doc/lib/libprofile.tex
+++ b/Doc/lib/libprofile.tex
@@ -361,7 +361,7 @@ Analysis of the profiler data is done using this class from the
% (This \stmodindex use may be hard to change ;-( )
\stmodindex{pstats}
-\begin{classdesc}{Stats}{filename\optional{, ...}}
+\begin{classdesc}{Stats}{filename\optional{, \moreargs}}
This class constructor creates an instance of a ``statistics object''
from a \var{filename} (or set of filenames). \class{Stats} objects are
manipulated by methods, in order to print useful reports.
@@ -398,7 +398,7 @@ statistics for these two entries are accumulated into a single entry.
\end{methoddesc}
-\begin{methoddesc}[Stats]{add}{filename\optional{, ...}}
+\begin{methoddesc}[Stats]{add}{filename\optional{, \moreargs}}
This method of the \class{Stats} class accumulates additional
profiling information into the current profiling object. Its
arguments should refer to filenames created by the corresponding
@@ -415,7 +415,7 @@ the same name on the \class{profile.Profile} class.
\versionadded{2.3}
\end{methoddesc}
-\begin{methoddesc}[Stats]{sort_stats}{key\optional{, ...}}
+\begin{methoddesc}[Stats]{sort_stats}{key\optional{, \moreargs}}
This method modifies the \class{Stats} object by sorting it according
to the supplied criteria. The argument is typically a string
identifying the basis of a sort (example: \code{'time'} or
@@ -551,7 +551,7 @@ is only ticking at a rate (typically) of about .001 seconds. Hence no
measurements will be more accurate than the underlying clock. If
enough measurements are taken, then the ``error'' will tend to average
out. Unfortunately, removing this first error induces a second source
-of error...
+of error.
The second problem is that it ``takes a while'' from when an event is
dispatched until the profiler's call to get the time actually