[issue4012] Minor errors in multiprocessing docs

Jesse Noller <[EMAIL PROTECTED]> added the comment: Warning added for georg's issue, all doc errors fixed on trunk, py3k and 2.6.1 maint. see r67419 -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]>

[issue4012] Minor errors in multiprocessing docs

Georg Brandl <[EMAIL PROTECTED]> added the comment: Fixed applyAsync and missing ] in r67335. ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Pyth

[issue4012] Minor errors in multiprocessing docs

Erick Tryzelaar <[EMAIL PROTECTED]> added the comment: 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. -- nosy: +erickt versions: +Python 3.0 ___ Python tracker

[issue4012] Minor errors in multiprocessing docs

Jesse Noller <[EMAIL PROTECTED]> added the comment: fix_up_logger doesn't exist in the port, but is used in the mp_distributing.py example ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue4012] Minor errors in multiprocessing docs

osvenskan <[EMAIL PROTECTED]> added the comment: 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/de

[issue4012] Minor errors in multiprocessing docs

Georg Brandl <[EMAIL PROTECTED]> added the comment: Fixed the "processing" name in r66939. ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-

[issue4012] Minor errors in multiprocessing docs

David Ripton <[EMAIL PROTECTED]> added the comment: 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.) -- nosy: +dripton ___ Python

[issue4012] Minor errors in multiprocessing docs

Kent Johnson <[EMAIL PROTECTED]> added the comment: On Thu, Oct 2, 2008 at 1:07 PM, Jesse Noller <[EMAIL PROTECTED]> wrote: > > Jesse Noller <[EMAIL PROTECTED]> added the comment: > > Which examples are you talking about Georg? I think you mean me, not Georg...I was referring to the example that

[issue4012] Minor errors in multiprocessing docs

Jesse Noller <[EMAIL PROTECTED]> added the comment: On Thu, Oct 2, 2008 at 1:10 PM, Georg Brandl <[EMAIL PROTECTED]> wrote: > > Georg Brandl <[EMAIL PROTECTED]> added the comment: > > I e.g. tried a minimal example with Pool.map(): > from multiprocessing import Pool p = Pool(5) def

[issue4012] Minor errors in multiprocessing docs

Jesse Noller <[EMAIL PROTECTED]> added the comment: Ok, let me take a look at that ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-lis

[issue4012] Minor errors in multiprocessing docs

Georg Brandl <[EMAIL PROTECTED]> 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 ... >>> p.map(f, [1,2,3]) Process PoolWorker-1: Traceback (most recent call last): File "/home/gbr/devel/python

[issue4012] Minor errors in multiprocessing docs

Jesse Noller <[EMAIL PROTECTED]> added the comment: Also, several things which are properties are still referred to as methods and include the () chars for the call ___ Python tracker <[EMAIL PROTECTED]>

[issue4012] Minor errors in multiprocessing docs

Jesse Noller <[EMAIL PROTECTED]> added the comment: Which examples are you talking about Georg? ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Py

[issue4012] Minor errors in multiprocessing docs

Georg Brandl <[EMAIL PROTECTED]> added the comment: 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)? _

[issue4012] Minor errors in multiprocessing docs

Changes by Jesse Noller <[EMAIL PROTECTED]>: -- assignee: georg.brandl -> jnoller nosy: +jnoller ___ Python tracker <[EMAIL PROTECTED]> ___

[issue4012] Minor errors in multiprocessing docs

New submission from Kent Johnson <[EMAIL PROTECTED]>: 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 a