summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEzio Melotti <ezio.melotti@gmail.com>2011-04-03 16:25:49 +0300
committerEzio Melotti <ezio.melotti@gmail.com>2011-04-03 16:25:49 +0300
commitc9a5272e8dc0aaa5d0ce63297b72292f4982db18 (patch)
treefc1097f885d1d0ea19205338320f2b4e92424a2a
parentd91a5caf0d8c8fa754d07d733f21c0e442b9067f (diff)
parent9481e4174191e43fbb2bff4c670bb6c604e86ae2 (diff)
downloadcpython-git-c9a5272e8dc0aaa5d0ce63297b72292f4982db18.tar.gz
Merge with 3.2
-rw-r--r--Doc/library/profile.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/library/profile.rst b/Doc/library/profile.rst
index 9c2b8de0cc..3931836f70 100644
--- a/Doc/library/profile.rst
+++ b/Doc/library/profile.rst
@@ -50,7 +50,7 @@ compatibility layer on top of the internal :mod:`_lsprof` module.
The profiler modules are designed to provide an execution profile for a given
program, not for benchmarking purposes (for that, there is :mod:`timeit` for
- resonably accurate results). This particularly applies to benchmarking
+ reasonably accurate results). This particularly applies to benchmarking
Python code against C code: the profilers introduce overhead for Python code,
but not for C-level functions, and so the C code would seem faster than any
Python one.