[issue13558] multiprocessing package incompatible with PyObjC

Ned Deily added the comment: Issue8713 proposes adding the option of using processes for multiprocessing rather than bare forks. Let's consolidate this issue with that one. -- resolution: -> duplicate stage: -> committed/rejected status: open -> closed superseder: -> multiprocessin

[issue13558] multiprocessing package incompatible with PyObjC

Ned Deily added the comment: (Reference original discussion in pyobjc-dev mailing list archived here: http://comments.gmane.org/gmane.comp.python.pyobjc.devel/5965) -- ___ Python tracker

[issue13558] multiprocessing package incompatible with PyObjC

Changes by Antoine Pitrou : -- nosy: +ned.deily versions: +Python 3.2, Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue13558] multiprocessing package incompatible with PyObjC

New submission from Trevor Bentley : The multiprocessing package appears to spawn a new process by calling only fork(). Apple's CoreFoundation libraries (and possibly more, I do not know the full extent) *require* new processes to be spawned with the full fork()+exec*() combo. When using PyO