diff options
| author | Mason <38963371+nosamproductions@users.noreply.github.com> | 2020-08-26 19:49:14 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-08-27 02:49:14 +0200 |
| commit | b260635b3db5715adf7a9a3df542c171fb7296ef (patch) | |
| tree | 971a6221134c9b0ec73ad8b5f998257c96447622 | |
| parent | 8c58d2a216ca2b5965361df9b8d8944bc7d4854d (diff) | |
| download | cpython-git-b260635b3db5715adf7a9a3df542c171fb7296ef.tar.gz | |
Add missing word (GH-21936)
"data to lost" -> "data to be lost"
| -rw-r--r-- | Doc/library/multiprocessing.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst index 28510acd52..f8e7556f25 100644 --- a/Doc/library/multiprocessing.rst +++ b/Doc/library/multiprocessing.rst @@ -861,7 +861,7 @@ For an example of the usage of queues for interprocess communication see 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. + data to be 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. |