diff options
author | Richard Oudkerk <shibturn@gmail.com> | 2013-06-24 17:12:57 (GMT) |
---|---|---|
committer | Richard Oudkerk <shibturn@gmail.com> | 2013-06-24 17:12:57 (GMT) |
commit | 7b69da72b8e48920697c8bb44165709ec6df6f8c (patch) | |
tree | cdedbfec1ff0c3dd81f615f70c9143f7fe66cc45 /Doc | |
parent | 64c25b4282219a1589275bf884b3cb6ffbed14c7 (diff) | |
download | cpython-7b69da72b8e48920697c8bb44165709ec6df6f8c.zip cpython-7b69da72b8e48920697c8bb44165709ec6df6f8c.tar.gz cpython-7b69da72b8e48920697c8bb44165709ec6df6f8c.tar.bz2 |
Clarify note and fix typo.
Diffstat (limited to 'Doc')
-rw-r--r-- | Doc/library/multiprocessing.rst | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst index 9061971..c034511 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` |