summaryrefslogtreecommitdiffstats
path: root/Doc/library/profile.rst
diff options
context:
space:
mode:
authorEzio Melotti <ezio.melotti@gmail.com>2011-04-03 13:24:22 (GMT)
committerEzio Melotti <ezio.melotti@gmail.com>2011-04-03 13:24:22 (GMT)
commit9481e4174191e43fbb2bff4c670bb6c604e86ae2 (patch)
tree988011c1977375ea8debf52074f8d4a544b90693 /Doc/library/profile.rst
parent6c94e6fb42a5318da5c736894ed0fa5d61f85e5f (diff)
parentb5ff3e4ce5f16ac9af5c682c6e8156393745f329 (diff)
downloadcpython-9481e4174191e43fbb2bff4c670bb6c604e86ae2.zip
cpython-9481e4174191e43fbb2bff4c670bb6c604e86ae2.tar.gz
cpython-9481e4174191e43fbb2bff4c670bb6c604e86ae2.tar.bz2
Merge with 3.1
Diffstat (limited to 'Doc/library/profile.rst')
-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 9c2b8de..3931836 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.