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 LambertDW
Recipients LambertDW, georg.brandl
Date 2008-09-29.05:21:22
SpamBayes Score 9.763985e-06
Marked as misclassified No
Message-id <1222665685.89.0.771974548734.issue3993@psf.upfronthosting.co.za>
In-reply-to
Content
http://docs.python.org/dev/3.0/library/multiprocessing.html#module-
multiprocessing

uses "print" statement in pre-version 3 form.  I can easily imagine 
that this and similar 2to3 bugs pervade the manual.


(If I insisted on foolish consistency I'd point out also that the 
multiprocessing guidelines recommend joining all processes started, 
but that a few items later under "joining processes that use queues" 
hides the parenthetical remark

"... (or simply remove the p.join() line).")


At any rate, I'm looking forward to the 3.0 release.  And I'm thrilled 
that the library modules seem to be evolving toward lumps that are 
commonly used together.
History
Date User Action Args
2008-09-29 05:21:26LambertDWsetrecipients: + LambertDW, georg.brandl
2008-09-29 05:21:25LambertDWsetmessageid: <1222665685.89.0.771974548734.issue3993@psf.upfronthosting.co.za>
2008-09-29 05:21:23LambertDWlinkissue3993 messages
2008-09-29 05:21:22LambertDWcreate