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 amorilia
Recipients amorilia, brian.curtin, rlibiez, santoso.wijaya, vstinner
Date 2011-10-05.18:15:36
SpamBayes Score 6.446431e-06
Marked as misclassified No
Message-id <1317838537.66.0.0157022031873.issue13081@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for also trying it out, Brian.

I feel there's little more I can do. I guess the multiprocessing module could be documented a bit better that join() ought to be called before the pool is deleted? Currently, the docs merely say:

"Wait for the worker processes to exit. One must call close() or terminate() before using join()." (http://docs.python.org/library/multiprocessing.html#multiprocessing.pool.multiprocessing.Pool.join)

Something along the following lines could be added:

"You must call join() when you no longer need the pool; otherwise, zombie processes may keep running."

I'm happy to provide a patch, if needed.
History
Date User Action Args
2011-10-05 18:15:37amoriliasetrecipients: + amorilia, vstinner, brian.curtin, santoso.wijaya, rlibiez
2011-10-05 18:15:37amoriliasetmessageid: <1317838537.66.0.0157022031873.issue13081@psf.upfronthosting.co.za>
2011-10-05 18:15:37amorilialinkissue13081 messages
2011-10-05 18:15:36amoriliacreate