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 DavidDecotigny
Recipients DavidDecotigny, jnoller
Date 2008-08-29.23:07:07
SpamBayes Score 0.00027564995
Marked as misclassified No
Message-id <1220051229.09.0.236623735385.issue3735@psf.upfronthosting.co.za>
In-reply-to
Content
I posted a recipe on ASPN: http://code.activestate.com/recipes/576462/
and Jesse, cheerleader for the inclusion of (multi)processing into
python-core, suggested that it could be interesting to add this feature
to the next pythons.
This recipe is based on version 0.52 of the standalone "processing"
package, and allows to avoid redundancy when multiple threads send the
same job requests to a pool of background worker processes. The recipe
details the why and the how.
Some notes on the implementation, though:
 - There is a "Begin/End workaround" section in the code, which aims at
working around a limitation of processing 0.52 (see comments and
docstring for details). I sent issue #014431 to the issue tracker for
processing on berlios, this would allow to get rid of this workaround
 - Read my comment #2 to the recipe, dealing with my thoughts of using
weak references
History
Date User Action Args
2008-08-29 23:07:09DavidDecotignysetrecipients: + DavidDecotigny, jnoller
2008-08-29 23:07:09DavidDecotignysetmessageid: <1220051229.09.0.236623735385.issue3735@psf.upfronthosting.co.za>
2008-08-29 23:07:08DavidDecotignylinkissue3735 messages
2008-08-29 23:07:07DavidDecotignycreate