This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | tkf |
|---|---|
| Recipients | docs@python, tkf |
| Date | 2013年04月20日.21:44:08 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1366494249.42.0.0654021028594.issue17805@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013年04月20日 21:44:09 | tkf | set | recipients: + tkf, docs@python |
| 2013年04月20日 21:44:09 | tkf | set | messageid: <1366494249.42.0.0654021028594.issue17805@psf.upfronthosting.co.za> |
| 2013年04月20日 21:44:09 | tkf | link | issue17805 messages |
| 2013年04月20日 21:44:09 | tkf | create | |