Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upFix typo in multiprocessing.pool.AsyncResult.successful doc. #17932
Conversation
Thanks for the PR @awecx. I confirmed from the source code that 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. |
This comment has been minimized.
This comment has been minimized.
Added @pitrou as a reviewer for the PR, since he's an active expert for the multiprocessing module. |
This comment has been minimized.
This comment has been minimized.
Thanks @aeros for the clarification. Indeed I should have proven the typo claim more clearly:
|
+1 |
This comment has been minimized.
This comment has been minimized.
miss-islington
commented
Jan 15, 2020
Thanks @awecx for the PR |
…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>
This comment has been minimized.
This comment has been minimized.
bedevere-bot
commented
Jan 15, 2020
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>
This comment has been minimized.
This comment has been minimized.
bedevere-bot
commented
Jan 15, 2020
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)
awecx commentedJan 9, 2020
•
edited by miss-islington
Since 3.7
successful
raises aValueError
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.
Automerge-Triggered-By: @pitrou