From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Wed, 15 Jan 2020 20:19:39 +0000 (-0800)
Subject: [3.7] Fix typo in multiprocessing.pool.AsyncResult.successful doc. (GH-17932) (GH... 
X-Git-Tag: v3.7.7rc1~90
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=74b95b6b320a739b75776c275d70deaa6330f5c1;p=thirdparty%2FPython%2Fcpython.git

[3.7] Fix typo in multiprocessing.pool.AsyncResult.successful doc. (GH-17932) (GH-18016)



Since 3.7 `successful` raises a `ValueError` as explained in the next text block from the documentation:

_Changed in version 3.7: If the result is not ready, ValueError is raised instead of AssertionError._

No issue associated with this PR.
Should be backported in 3.7 and 3.8.
(cherry picked from commit dc0284ee8f7a270b6005467f26d8e5773d76e959)


Co-authored-by: Antoine <43954001+awecx@users.noreply.github.com>

Automerge-Triggered-By: @pitrou
---

diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst
index 9bed380117ed..6fd509a00caf 100644
--- a/Doc/library/multiprocessing.rst
+++ b/Doc/library/multiprocessing.rst
@@ -2252,7 +2252,7 @@ with the :class:`Pool` class.
    .. method:: successful()
 
       Return whether the call completed without raising an exception.  Will
-      raise :exc:`AssertionError` if the result is not ready.
+      raise :exc:`ValueError` if the result is not ready.
 
 The following example demonstrates the use of a pool::