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 r.david.murray
Recipients cool-RR, ezio.melotti, jnoller, petri.lehtinen, r.david.murray, terry.reedy
Date 2011-05-27.16:31:06
SpamBayes Score 0.00010113019
Marked as misclassified No
Message-id <1306513867.33.0.987304287806.issue11969@psf.upfronthosting.co.za>
In-reply-to
Content
REPL is the Python interactive prompt in this case (REPL is Read Eval Print Loop).  So Jesse is saying that using multiprocessing from the REPL (at least on Windows) isn't supported.  This is because on Windows multiprocessing needs to re-import the main program in order to start the function in a worker process.  When using the REPL, there is no main program from which to import the function.

The test case failing on windows may or may not be a related issue; I'm not familiar enough with mulitprocessing to say.
History
Date User Action Args
2011-05-27 16:31:07r.david.murraysetrecipients: + r.david.murray, terry.reedy, jnoller, ezio.melotti, cool-RR, petri.lehtinen
2011-05-27 16:31:07r.david.murraysetmessageid: <1306513867.33.0.987304287806.issue11969@psf.upfronthosting.co.za>
2011-05-27 16:31:06r.david.murraylinkissue11969 messages
2011-05-27 16:31:06r.david.murraycreate