classification
Title: No such class: multiprocessing.pool.AsyncResult
Type: Stage: resolved
Components: Documentation Versions: Python 3.3, Python 3.4, Python 2.7
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, python-dev, sbt, tkf
Priority: normal Keywords: patch

Created on 2013-04-20 21:44 by tkf, last changed 2013-05-06 11:27 by sbt. This issue is now closed.

Files
File name Uploaded Description Edit
ApplyResult.patch tkf, 2013-04-20 21:44
Messages (3)
msg187466 - (view) Author: Takafumi Arakaki (tkf) Date: 2013-04-20 21:44
Document mentions AsyncResult but there is no such class.
http://docs.python.org/2/library/multiprocessing.html#multiprocessing.pool.AsyncResult

You can check it by simply running:
python -c 'from multiprocessing.pool import AsyncResult'

I think it means ApplyResult so I made a patch (attached).

Note that there managers.py also uses name 'AsyncResult':
% hg grep AsyncResult
Doc/library/multiprocessing.rst:83232:.. class:: AsyncResult
Lib/multiprocessing/managers.py:81039:    'apply_async': 'AsyncResult',
Lib/multiprocessing/managers.py:81039:    'map_async': 'AsyncResult',
Lib/multiprocessing/managers.py:81039:    'starmap_async': 'AsyncResult',
Lib/multiprocessing/managers.py:81039:SyncManager.register('AsyncResult', create_method=False)

Probably renaming them would be better?
msg188265 - (view) Author: Richard Oudkerk (sbt) * (Python committer) Date: 2013-05-02 13:26
It might be simplest to make the implementation match the docs by making AsyncResult an alias for ApplyResult.
msg188510 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2013-05-06 11:15
New changeset 2684176519ef by Richard Oudkerk in branch '2.7':
Issue #17805: Add AsyncResult alias for ApplyResult
http://hg.python.org/cpython/rev/2684176519ef

New changeset bb4bb2db6106 by Richard Oudkerk in branch '3.3':
Issue #17805: Add AsyncResult alias for ApplyResult
http://hg.python.org/cpython/rev/bb4bb2db6106
History
Date User Action Args
2013-05-06 11:27:26sbtsetstatus: open -> closed
resolution: fixed
stage: resolved
2013-05-06 11:15:19python-devsetnosy: + python-dev
messages: + msg188510
2013-05-02 13:26:29sbtsetmessages: + msg188265
2013-04-20 22:07:18ned.deilysetnosy: + sbt

versions: - Python 2.6, Python 3.1, Python 3.2, Python 3.5
2013-04-20 21:44:09tkfcreate