traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge with 3.2

This commit is contained in:
Ezio Melotti 2011-04-03 16:25:49 +03:00
parent d91a5caf0d 9481e41741
commit c9a5272e8d
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Doc/library/profile.rst
View File

@ -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 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 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, 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 but not for C-level functions, and so the C code would seem faster than any
Python one. Python one.