I'm wondering if there is a way to "repair" the broken interaction
between pyobjc and the multiprocessing module I'm trying out.
Trying to fire up a runloop inside a forked process (a
multiprocessing.Process object) gives the following:
The process has forked and you cannot use this CoreFoundation
functionality safely. You MUST exec().
Break on
__THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__
() to debug.
This page explains it well enough:
http://lists.apple.com/archives/cocoa-dev//2005/Jan/msg00676.html
The question is, from the child python process can I do the equiv of
exec() to fix the state of the CoreFoundation libraries?
I've tried reloading() the Cocoa module - but that did not suffice.
-Preston
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
