homepage

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 ethan.furman
Recipients amaury.forgeotdarc, ethan.furman, jnoller
Date 2012年10月16日.12:16:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1350389817.55.0.995425148307.issue16246@psf.upfronthosting.co.za>
In-reply-to
Content
On Windows multiprocessing has a well known limitation: because there is no fork() new shells must be invoked, and if the call that ultimately starts multiprocessing is not guarded by an `if __name__ == '__main___'` check an infinite loops results and you have a very nice brick instead of a computer.
On Stackoverflow I proposed a work-around [1], which is basically to check if an environment variable exists (MP_GUARD is this case), and if it does raise an exception.
I'm going to try and merge that into multiprocessing itself. Are there any other platforms besides Windows where this is a problem?
[1] http://stackoverflow.com/q/12852643/208880 
History
Date User Action Args
2012年10月16日 12:16:57ethan.furmansetrecipients: + ethan.furman, amaury.forgeotdarc, jnoller
2012年10月16日 12:16:57ethan.furmansetmessageid: <1350389817.55.0.995425148307.issue16246@psf.upfronthosting.co.za>
2012年10月16日 12:16:57ethan.furmanlinkissue16246 messages
2012年10月16日 12:16:57ethan.furmancreate

AltStyle によって変換されたページ (->オリジナル) /