In the docs for AsyncResult
http://docs.python.org/dev/library/multiprocessing.html#multiprocessing.pool.AsyncResult

"get([timeout)" is missing a ]

In the example following, it refers to pool.applyAsync() in two places;
the docs spell this apply_async(), one of them must be wrong :-)

There's also an applyAsync left in the introductory Pool example.

Jesse, while you're at it, could you please add a blurb that some
examples won't work when tried at the interactive interpreter (and
perhaps also why)?

Which examples are you talking about Georg?

Also, several things which are properties are still referred to as methods 
and include the () chars for the call

I e.g. tried a minimal example with Pool.map():

>>> from multiprocessing import Pool
>>> p = Pool(5)
>>> def f(x):
...  return x*x
...
>>> p.map(f, [1,2,3])
Process PoolWorker-1:
Traceback (most recent call last):
  File "/home/gbr/devel/python/Lib/multiprocessing/process.py", line
231, in _bootstrap
    self.run()
  File "/home/gbr/devel/python/Lib/multiprocessing/process.py", line 88,
in run
    self._target(*self._args, **self._kwargs)
  File "/home/gbr/devel/python/Lib/multiprocessing/pool.py", line 57, in
worker
Process PoolWorker-2:

[some more exceptions]

    task = get()
  File "/home/gbr/devel/python/Lib/multiprocessing/queues.py", line 339,
in get
    return recv()
AttributeError: 'module' object has no attribute 'f'

And then the prompt doesn't reappear.

Ok, let me take a look at that

On Thu, Oct 2, 2008 at 1:10 PM, Georg Brandl <report@bugs.python.org> wrote:
>
> Georg Brandl <georg@python.org> added the comment:
>
> I e.g. tried a minimal example with Pool.map():
>
>>>> from multiprocessing import Pool
>>>> p = Pool(5)
>>>> def f(x):
> ...  return x*x
>

I'll add a note. I'm going to file a separate bug, I don't think that
should happen and it's fairly embarrassing that it does.

On Thu, Oct 2, 2008 at 1:07 PM, Jesse Noller <report@bugs.python.org> wrote:
>
> Jesse Noller <jnoller@gmail.com> added the comment:
>
> Which examples are you talking about Georg?

I think you mean me, not Georg...I was referring to the example that
immediately follows
http://docs.python.org/library/multiprocessing.html#multiprocessing.pool.AsyncResult.successful

Also, two of the example code blurbs in that page still refer to the
module as "processing" instead of "multiprocessing".  (Search for
"import processing" to find them.)

Fixed the "processing" name in r66939.

The Synchronization primitives section should mention that
sem_timedwait() isn't supported under OS X <=10.5.5 (and possibly later
versions) so as a result timeouts passed to acquire() will be ignored
(or raise an error?)

http://docs.python.org/dev/library/multiprocessing.html#synchronization-primitives

fix_up_logger doesn't exist in the port, but is used in the mp_distributing.py example

fyi, the multiprocessing docs also refer to applyAync, but the function 
was renamed to apply_async. This is also in the python 3.0 docs.

Fixed applyAsync and missing ] in r67335.

Warning added for georg's issue, all doc errors fixed on trunk, py3k and 
2.6.1 maint. see r67419