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.

classification
Title: _call_method() in multiprocessing documentation
Type: behavior Stage:
Components: Documentation Versions: Python 3.0, Python 2.6
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: georg.brandl Nosy List: beazley, benjamin.peterson, georg.brandl
Priority: normal Keywords:

Created on 2008-12-18 19:09 by beazley, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (3)
msg78038 - (view) Author: David M. Beazley (beazley) Date: 2008-12-18 19:09
The documentation for "Proxy Objects" in the multiprocessing module 
describes a method "_call_method" and gives various examples.   The only 
problem is that the method is actually called "_callmethod" (i.e., no 
underscore between "call" and "method").
msg78039 - (view) Author: David M. Beazley (beazley) Date: 2008-12-18 19:43
The _get_value() method is also in error.  It's called "_getvalue()" in 
the source code.
msg78053 - (view) Author: Benjamin Peterson (benjamin.peterson) * (Python committer) Date: 2008-12-19 02:32
Thanks for the report! Fixed in r67849.
History
Date User Action Args
2022-04-11 14:56:42adminsetgithub: 48944
2008-12-19 02:32:10benjamin.petersonsetstatus: open -> closed
nosy: + benjamin.peterson
resolution: fixed
messages: + msg78053
2008-12-18 19:43:53beazleysetmessages: + msg78039
2008-12-18 19:09:56beazleycreate