summaryrefslogtreecommitdiff
path: root/Doc
diff options
context:
space:
mode:
authorRichard Oudkerk <shibturn@gmail.com>2013-06-24 18:12:57 +0100
committerRichard Oudkerk <shibturn@gmail.com>2013-06-24 18:12:57 +0100
commit7b69da72b8e48920697c8bb44165709ec6df6f8c (patch)
treecdedbfec1ff0c3dd81f615f70c9143f7fe66cc45 /Doc
parent64c25b4282219a1589275bf884b3cb6ffbed14c7 (diff)
downloadcpython-git-7b69da72b8e48920697c8bb44165709ec6df6f8c.tar.gz
Clarify note and fix typo.
Diffstat (limited to 'Doc')
-rw-r--r--Doc/library/multiprocessing.rst5
1 files changed, 3 insertions, 2 deletions
diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst
index 90619717b2..c0345116e0 100644
--- a/Doc/library/multiprocessing.rst
+++ b/Doc/library/multiprocessing.rst
@@ -520,8 +520,9 @@ Note that one can also create a shared queue by using a manager object -- see
When an object is put on a queue, the object is pickled and a
background thread later flushes the pickled data to an underlying
pipe. This has some consequences which are a little surprising,
- but should not cause any pratical difficulties -- you can always
- use a managed queue if they really bother you.
+ but should not cause any practical difficulties -- if they really
+ bother you then you can instead use a queue created with a
+ :ref:`manager <multiprocessing-managers>`.
(1) After putting an object on an empty queue there may be an
infinitessimal delay before the queue's :meth:`~Queue.empty`