From d6c1d57195d907a8187442cd2f3e9d9575d6b4a8 Mon Sep 17 00:00:00 2001 From: Raymond Hettinger Date: Tue, 29 Mar 2011 17:30:01 -0700 Subject: Issue 11713: clarify docstring for collections.deque() --- Modules/_collectionsmodule.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Modules/_collectionsmodule.c b/Modules/_collectionsmodule.c index 1227de0..b5f2a69 100644 --- a/Modules/_collectionsmodule.c +++ b/Modules/_collectionsmodule.c @@ -913,7 +913,7 @@ static PyMethodDef deque_methods[] = { PyDoc_STRVAR(deque_doc, "deque(iterable[, maxlen]) --> deque object\n\ \n\ -Build an ordered collection accessible from endpoints only."); +Build an ordered collection with optimized access from its endpoints."); static PyTypeObject deque_type = { PyVarObject_HEAD_INIT(NULL, 0) -- cgit v0.12 From b5ff3e4ce5f16ac9af5c682c6e8156393745f329 Mon Sep 17 00:00:00 2001 From: Ezio Melotti Date: Sun, 3 Apr 2011 16:20:21 +0300 Subject: Fix typo noticed by Sandro Tosi. --- Doc/library/profile.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/library/profile.rst b/Doc/library/profile.rst index c5e5dd5..82cc2eb 100644 --- a/Doc/library/profile.rst +++ b/Doc/library/profile.rst @@ -48,7 +48,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. -- cgit v0.12