sturlamolden <[EMAIL PROTECTED]> writes: > If I use my main interpreter to delegate a task to one of its > embedded 'children', its GIL will be released while it is waiting > for the answer. Associating each embedded interpreter with a > threading.Thread is all that remains. The GIL is released while the > thread operating the child interpreter is blocked.
Have you tackled the communication problem? The way I see it, one interpreter cannot "see" objects created in the other because they have separate pools of ... everything. They can communicate by passing serialized objects through ctypes, but that sounds like the solutions that use processes. -- http://mail.python.org/mailman/listinfo/python-list
