You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed in #2422, the solution here is to ensure that the zmq sockets are never used in a forked process. This should be possible by checking os.getpid in the right places before touching the sockets.
forward stdout from forked processes
uses zmq instead of multiprocessing, because mp has too many issues.
- messages are sent via PUSH/PULL from subprocesses
- messages are sent at flush time, not at write time
- subprocess messages
- no threads, no sync events, etc.
some basic tests are included
closesipython#2438
Printing to stdout when in multiprocessing crashes Ipython notebook kernel.
Seems to occur both in 0.13 and 1981689 (current Git master)
And in notebook:
The notebook process prints this:
mailbox.cpp seems to be inside ZMQ/PyZMQ (tried with versions zmq-2.2.0 & pyzmq-2.2.0.1 and zmq-2.1.11 & pyzmq-2.1.7).
This works properly on the Ipython & Python command-line shells.
The text was updated successfully, but these errors were encountered: