summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGuido van Rossum <guido@python.org>1997-06-02 17:29:12 (GMT)
committerGuido van Rossum <guido@python.org>1997-06-02 17:29:12 (GMT)
commitbac80022e461247de1294cc37168c2a600511461 (patch)
tree6dab2836c44b066591c0c6da6ef77a4cce19f5ad
parentf967bf63f8b873fefc3c20a82546c44c608807b2 (diff)
downloadcpython-bac80022e461247de1294cc37168c2a600511461.zip
cpython-bac80022e461247de1294cc37168c2a600511461.tar.gz
cpython-bac80022e461247de1294cc37168c2a600511461.tar.bz2
Mention use of profile.py to run a script (AMK).
-rw-r--r--Doc/lib/libprofile.tex4
-rw-r--r--Doc/libprofile.tex4
2 files changed, 8 insertions, 0 deletions
diff --git a/Doc/lib/libprofile.tex b/Doc/lib/libprofile.tex
index da0c294..7cd3c6b 100644
--- a/Doc/lib/libprofile.tex
+++ b/Doc/lib/libprofile.tex
@@ -120,6 +120,10 @@ function:
profile.run("foo()", 'fooprof')
\end{verbatim}
+\code{profile.py} can also be invoked as
+a script to profile another script. For example:
+\code{python /usr/local/lib/python1.4/profile.py myscript.py}
+
When you wish to review the profile, you should use the methods in the
\code{pstats} module. Typically you would load the statistics data as
follows:
diff --git a/Doc/libprofile.tex b/Doc/libprofile.tex
index da0c294..7cd3c6b 100644
--- a/Doc/libprofile.tex
+++ b/Doc/libprofile.tex
@@ -120,6 +120,10 @@ function:
profile.run("foo()", 'fooprof')
\end{verbatim}
+\code{profile.py} can also be invoked as
+a script to profile another script. For example:
+\code{python /usr/local/lib/python1.4/profile.py myscript.py}
+
When you wish to review the profile, you should use the methods in the
\code{pstats} module. Typically you would load the statistics data as
follows: