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 valhallasw
Recipients ac.james, jnoller, valhallasw
Date 2012-03-10.18:26:45
SpamBayes Score 1.534643e-05
Marked as misclassified No
Message-id <1331404006.01.0.986632437081.issue6147@psf.upfronthosting.co.za>
In-reply-to
Content
Two questions:
(1) can this be at least be added as a big fat warning in the documentation?
(2) would it be a reasonable option to let either
  (a) the creation of a Pool
  (b) executing something using the Pool
cause an exception when it happens during the import of the function to run?

I think it makes sense to prevent any accidental forkbombs, especially if they are /this/ easy to create. Untested (for obvious reasons...), but this should be enough:

import multiprocessing
def x(val):
   return val
multiprocessing.Pool().map(x, range(10))
History
Date User Action Args
2012-03-10 18:26:46valhallaswsetrecipients: + valhallasw, jnoller, ac.james
2012-03-10 18:26:46valhallaswsetmessageid: <1331404006.01.0.986632437081.issue6147@psf.upfronthosting.co.za>
2012-03-10 18:26:45valhallaswlinkissue6147 messages
2012-03-10 18:26:45valhallaswcreate