diff options
author | Richard Oudkerk <shibturn@gmail.com> | 2013-07-02 12:01:31 (GMT) |
---|---|---|
committer | Richard Oudkerk <shibturn@gmail.com> | 2013-07-02 12:01:31 (GMT) |
commit | 771b961d4ea45889606992112002c6de0b5c358b (patch) | |
tree | 536e077d5e1f4e8fdb129de2bcfea46752d766d2 | |
parent | b0be62453f2608e5ba0718f5c49be7e4895ae590 (diff) | |
parent | d7d3f376dd653ab7534dbdcaae14f49987cbd28d (diff) | |
download | cpython-771b961d4ea45889606992112002c6de0b5c358b.zip cpython-771b961d4ea45889606992112002c6de0b5c358b.tar.gz cpython-771b961d4ea45889606992112002c6de0b5c358b.tar.bz2 |
Issue #14206: Clarify docs for Queue.join_cancel_thread().
-rw-r--r-- | Doc/library/multiprocessing.rst | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst index 1078463..f659eac 100644 --- a/Doc/library/multiprocessing.rst +++ b/Doc/library/multiprocessing.rst @@ -659,6 +659,13 @@ For an example of the usage of queues for interprocess communication see the background thread from being joined automatically when the process exits -- see :meth:`join_thread`. + A better name for this method might be + ``allow_exit_without_flush()``. It is likely to cause enqueued + data to lost, and you almost certainly will not need to use it. + It is really only there if you need the current process to exit + immediately without waiting to flush enqueued data to the + underlying pipe, and you don't care about lost data. + .. class:: SimpleQueue() |