Fix typo in multiprocessing.pool.AsyncResult.successful doc.#17932
Conversation
There was a problem hiding this comment.
Thanks for the PR @awecx.
I confirmed from the source code that AsyncResult.successful() does indeed raise a ValueError instead of an AssertionError:
cpython/Lib/multiprocessing/pool.py
Lines 753 to 756 in a796d8e
LGTM. This is also present in the 3.8 and 3.7 branches, so this PR should be backported to those versions as well.
|
Added @pitrou as a reviewer for the PR, since he's an active expert for the multiprocessing module. |
Thanks @aeros for the clarification. Indeed I should have proven the typo claim more clearly: |
|
Thanks @awecx for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7, 3.8. |
…H-17932) 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 dc0284e) Co-authored-by: Antoine <43954001+awecx@users.noreply.github.com>
|
GH-18015 is a backport of this pull request to the 3.8 branch. |
…H-17932) 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 dc0284e) Co-authored-by: Antoine <43954001+awecx@users.noreply.github.com>
|
GH-18016 is a backport of this pull request to the 3.7 branch. |
…H-17932) (GH-18015) 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 dc0284e) Co-authored-by: Antoine <43954001+awecx@users.noreply.github.com> Automerge-Triggered-By: @pitrou
…H-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 dc0284e) Co-authored-by: Antoine <43954001+awecx@users.noreply.github.com> Automerge-Triggered-By: @pitrou
Fix typo in multiprocessing.pool.AsyncResult.successful doc. (pythonGH-17932)
…H-17932) 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.
Since 3.7
successfulraises aValueErroras 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.
Automerge-Triggered-By: @pitrou