summaryrefslogtreecommitdiffstats
path: root/Doc/libprofile.tex
diff options
context:
space:
mode:
authorGuido van Rossum <guido@python.org>1995-03-22 15:48:46 (GMT)
committerGuido van Rossum <guido@python.org>1995-03-22 15:48:46 (GMT)
commitcca8d2bb48342a2e88be7259af3c75871b992ce8 (patch)
treebedebe6f0750d8b80857f0893d7c8c126c3a8415 /Doc/libprofile.tex
parentb022eb54e6544499c9f689a3b4343380d28c8852 (diff)
downloadcpython-cca8d2bb48342a2e88be7259af3c75871b992ce8.zip
cpython-cca8d2bb48342a2e88be7259af3c75871b992ce8.tar.gz
cpython-cca8d2bb48342a2e88be7259af3c75871b992ce8.tar.bz2
some new material
Diffstat (limited to 'Doc/libprofile.tex')
-rw-r--r--Doc/libprofile.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/libprofile.tex b/Doc/libprofile.tex
index ecf41c3..3cd4296 100644
--- a/Doc/libprofile.tex
+++ b/Doc/libprofile.tex
@@ -500,7 +500,7 @@ 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 builtin functions) will be charged to the
-Python function that was invoked the C code. If the C code calls out
+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.