gipc: child processes and IPC for gevent

Table of contents:

This documentation applies to gipc 0.5.0. It was built on October 22, 2014.

About gipc

gipc provides convenient child process management in the context of gevent. gipc (pronunciation “gipsy”) is a Python package tested on CPython 2.6 and 2.7 on Linux as well as on Windows.

What is gipc good for?

There is plenty of motivation for using multiple processes in event-driven architectures. The assumption behind gipc is that applying multiple processes that communicate among each other (whereas each process has its own event loop) can be a decent solution for many types of problems. First of all, it helps decoupling system components by making each process responsible for one part of the architecture only. Furthermore, even a generally I/O-intense application might at some point become CPU bound. In these cases, the distribution of tasks among multiple processes is an efficient way to make use of multi-core machines and easily increases the application’s performance.

However, canonical usage of Python’s multiprocessing module within a gevent-powered application may raise various problems and most likely breaks the application in many ways. gipc is developed with the motivation to solve these issues transparently and make using gevent in combination with multiprocessing-based child processes and inter-process communication (IPC) a no-brainer again:

  • With gipc, multiprocessing.Process-based child processes can safely be created and monitored anywhere within your gevent-powered application. Malicious side-effects of child process creation in the context of gevent are prevented.
  • The API of multiprocessing.Process objects is provided in a gevent-cooperative fashion.
  • gevent natively works in children.
  • gipc comes up with a pipe-based transport layer for gevent-cooperative IPC.
  • gipc is lightweight and simple to integrate.

In the following code snippet, a Python object is sent from a greenlet in the main process through a pipe to a child process:

import gevent
import gipc

def child(reader):
    assert reader.get() == 0

if __name__ == "__main__":
    with gipc.pipe() as (reader, writer):
        writelet = gevent.spawn(lambda w: w.put(0), writer)
        readchild = gipc.start_process(target=child, args=(reader,))

Although quite simple, this code would have various negative side-effects if used with the canonical multiprocessing API instead of gipc.start_process() and gipc.pipe(), as outlined in the next paragraph.

What are the challenges and what is gipc’s approach?


Depending on the operating system, child process creation via Python’s multiprocessing in the context of gevent requires special treatment. Most care is needed on POSIX-compliant systems. There, a fork might yield a faulty libev event loop state in the child. Most noticeable, greenlets spawned before forking are cloned and haunt in the child upon context switch. Consider this code running on Unix (tested with Python 2.7 & gevent 1.0):

import gevent
import multiprocessing

def child(c):
    assert c.recv() == 0
    assert c.recv() == 0

if __name__ == "__main__":
    def writelet(c):
    c1, c2 = multiprocessing.Pipe()
    writelet = gevent.spawn(writelet, c1)
    readchild = multiprocessing.Process(target=child, args=(c2,))

It runs without error. Although the code intends to send only one message to the child through a multiprocessing Pipe, the two assert statements verify that the child actually receives two times the same message. One message is sent – as intended – from the writelet in the parent through the c1 end of the pipe. It is retrieved at the c2 end of the pipe in the child. The other message is sent from the spooky writelet clone in the child. It is also written to the c1 end of the pipe which has implicitly been duplicated during forking. Greenlet clones in the child of course only run when a context switch is triggered; in this case via gevent.sleep(0). As you can imagine, this behavior in general might lead to a wide range of side-effects and tedious debugging sessions.

In addition, the code above contains several non-cooperatively blocking method calls: readchild.join() as well as the send()/recv() calls (of multiprocessing.Connection objects in general) block the calling greenlet non-cooperatively and do not allow for context switches into other greenlets.


gipc overcomes these and other issues for you transparently and in a straight- forward fashion: basically, children start off with a fresh gevent state before entering the user-given target function. More specifically, as one of the first actions, children destroy the inherited gevent hub as well as the inherited libev event loop and create their own fresh versions of these objects. This way, inherited greenlets as well as libev watchers become orphaned – the fresh hub and event loop are not connected to them anymore. Consequently, execution of code related to these inherited greenlets and watchers is efficiently prevented without the need to deactivate or kill them one by one.

Furthermore, on POSIX-compliant systems, gipc entirely avoids multiprocessing’s child monitoring implementation (which is based on wait) and instead uses libev’s wonderful child watcher system (based on SIGCHLD signal transmission), enabling gevent-cooperative waiting for child termination.

For the sake of gevent-cooperative inter-process communication, gipc uses efficient pipe-based data transport channels with non-blocking I/O. gipc takes care of closing dispensable pipe handles (file descriptors) in the parent as well as in the child after forking.

Overall, gipc’s main goal is to allow for the integration of child processes in your gevent-powered application via a simple API – on POSIX-compliant systems as well as on Windows.


gipc’s usage is pretty simple. Its interface is clear and slim. Make yourself comfortable with gipc.start_process() and gipc.pipe() by going through the examples and the API section.

Technical notes

  • gipc uses classical anonymous pipes as transport layer for gevent-cooperative communication between greenlets and/or processes. By default, a binary pickle protocol is used for transmitting arbitrary objects. Reading and writing on pipes is done with gevent‘s cooperative versions of and os.write() (on POSIX-compliant systems they use non-blocking I/O, on Windows a thread pool is used). On Linux, my test system (Xeon E5630) achieved a payload transfer rate of 1200 MB/s and a message transmission rate of 100.000 messages/s through one pipe between two processes.
  • Child process creation and invocation is done via a thin wrapper around multiprocessing.Process. On Unix, the inherited gevent hub as well as the libev event loop become destroyed and re-initialized in the child before execution of the target function.
  • On POSIX-compliant systems, gevent-cooperative child process monitoring is based on libev child watchers (this affects the is_alive() and join() methods).
  • Convenience features such as a context manager for pipe handles or timeout controls based on gevent.Timeout are available.
  • Any read/write operation on a pipe is gevent.lock.Semaphore-protected and therefore greenlet-/thread safe and atomic.
  • The auto-close behavior (gipc automatically closes handles in the parent if provided to the child, and also closes those in the child that were not explicitly transferred to it) might be a limitation in some cases. At the same time, it automatically prevents file descriptor leakage and forces developers to make deliberate choices about which handles should be transferred explicitly.
  • gipc obeys semantic versioning 2.
  • Although gipc is in an early development phase, I found it to work stable already. The unit test suite aims to cover all of gipc’s features within a clean gevent environment. More complex application scenarios, however, are not covered so far. Please let me know in which cases gipc + gevent fails for you.

Is gipc reliable?

As of version 0.3, I am not aware of severe issues. To my knowledge, gipc has already been deployed in serious projects. Generally, you should be aware of the fact that mixing any of fork, threads, greenlets and an event loop library such as libev bears the potential for various kinds of corner-case disasters. One could argue that fork() in the context of libev without doing a clean exec in the child already is broken design. However, many people would like to do exactly this and gipc’s basic approach has proven to work in such cases. gipc is developed with a strong focus on reliability and with best intentions in mind. Via unit testing it has been validated to work reliably in scenarios of low and medium complexity. Of course, gipc cannot rescue an a priori ill-posed approach. Now it is up to you to evaluate gipc in the context of your project – please share your experience.

Code, requirements, download, installation

gipc’s Mercurial repository is hosted at Bitbucket.

gipc requires:

  • gevent >= 1.0 (currently, gipc is tested against gevent 1.0). Download recent gevent releases here or from PyPI.
  • CPython 2.6 or 2.7 (Python 3 will be supported as soon as gevent supports it). Unit tests are made sure to work on Linux as well as Windows.

The latest gipc release from PyPI can be pulled and installed via pip:

$ pip install gipc

pip can also install the current development version of gipc:

$ pip install hg+

Notes for Windows users

  • The _GIPCReader.get() timeout feature is not available.
  • “Non-blocking I/O” is imitated by outsourcing blocking I/O calls to threads in a gevent thread pool. Compared to native non-blocking I/O as is available on POSIX-compliant systems, this leads to a significant messaging performance drop.

Windows I/O Completion Ports (IOCP) could solve both issues in an elegant way. Currently, gevent is built on top of libev which does not support IOCP. In the future, however, gevent might become libuv-backed. libuv supports IOCP and would allow for running the same gevent code on Windows as on POSIX-compliant systems. Furthermore, if gevent went with libuv, the strengths of both, the node.js and the gevent worlds would be merged. Denis Bilenko, the maintainer of gevent, seems to be open to such a transition and the first steps are already done.

Author, license, contact

gipc is written and maintained by Jan-Philip Gehrcke and licensed under an MIT license (see LICENSE file for details). Your feedback is highly appreciated. You can contact me at or use the Bitbucket issue tracker.


Note that these examples are designed with the motivation to demonstrate the API and capabilities of gipc, rather than showing interesting use cases.

gipc.pipe()-based messaging from greenlet in parent to child

Very basic gevent and gipc concepts are explained by means of the following simple messaging example:

import gevent
import gipc

def main():
    with gipc.pipe() as (r, w):
        p = gipc.start_process(target=child_process, args=(r, ))
        wg = gevent.spawn(writegreenlet, w)
        except KeyboardInterrupt:

def writegreenlet(writer):
    while True:
        writer.put("written to pipe from a greenlet running in the main process")

def child_process(reader):
    while True:
        print "Child process got message from pipe:\n\t'%s'" % reader.get()

if __name__ == "__main__":

The context manager with gipc.pipe() as (r, w) creates a pipe with read handle r and write handle w. On context exit (latest) the pipe ends will be closed properly.

After creating the pipe context, the above code spawns a child process via gipc.start_process(). The child process is instructed to execute the target function named child_process whereas the pipe read handle r is provided as an argument to this target function. Within child_process() an endless loop waits for objects on the read end of the pipe via the cooperatively blocking call to reader.get(). Upon retrieval, it immediately writes their string representation to stdout.

After invocation of the the child process (represented by an object bound to name p), a greenlet wg is spawned within the main process. This greenlet executes the function writegreenlet, whereas the pipe write handle w is provided as an argument. Within this greenlet, one string per second is written to the write end of the pipe.

After spawning wg, p.join() is called immediately in the parent process. p.join() is blocking cooperatively, i.e. it allows for a context switch into the write greenlet (this actually is the magic behind gevent/greenlets). Hence, the write greenlet is ‘running’ while p.join() cooperatively waits for the child process to terminate. The write greenlet spends most of its time in gevent.sleep(), which is also blocking cooperatively, allowing for context switches back to the main greenlet in the parent process, which is executing p.join(). In this state, one message per second is passed between parent and child until a KeyboardInterrupt exception is raised in the parent.

Upon KeyboardInterrupt, the parent first kills the write greenlet and blocks cooperatively until it has stopped. Then it terminates the child process (via SIGTER on Unix) and waits for it to exit via p.join().

Serving multiple clients (in child) from one server (in parent)

For pure API and reliability demonstration purposes, this example implements TCP communication between a server in the parent process and multiple clients in one child process:

  1. gevent’s StreamServer is started in a greenlet within the initial (parent) process. For each connecting client, it receives one newline-terminated message and echoes it back.
  2. A child process is started using gipc. Its starting point is the function clientprocess. There, N TCP clients are started concurrently from N greenlets.
  3. Each client sends one message, validates the echo response and terminates.
  4. The child process terminates.
  5. After the child process is joined in the parent, the server is killed.
  6. The server greenlet is joined.
import gevent
from gevent.server import StreamServer
from gevent import socket
import gipc
import time

PORT = 1337
N_CLIENTS = 1000

def serve(sock, addr):
    f = sock.makefile()

def server():
    ss = StreamServer(('localhost', PORT), serve).serve_forever()

def clientprocess():
    t1 = time.time()
    clients = [gevent.spawn(client) for _ in xrange(N_CLIENTS)]
    duration = time.time()-t1
    print "%s clients served within %.2f s." % (N_CLIENTS, duration)

def client():
    sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
    sock.connect(('localhost', PORT))
    f = sock.makefile()
    assert f.readline() == MSG

if __name__ == "__main__":
    s = gevent.spawn(server)
    c = gipc.start_process(clientprocess)

Output on my test machine: 1000 clients served within 0.54 s.

Time-synchronization between processes

Child process creation may take a significant amount of time, especially on Windows. The exact amount of time is not predictable.

When code in the parent should only proceed in the moment the code in the child has reached a certain state, the proper way to tackle this is a bidirectional synchronization handshake:

  • Process A sends a synchronization request to process B and waits for an acknowledgment response. It proceeds upon retrieval.
  • Process B sends the acknowledgment in the moment it retrieves the sync request and proceeds.

This concept can easily be implemented using a bidirectional gipc.pipe():

import gevent
import gipc
import time

def main():
    with gipc.pipe(duplex=True) as (cend, pend):
        # `cend` is the channel end for the child, `pend` for the parent.
        p = gipc.start_process(writer_process, args=(cend,))
        # Synchronize with child process.
        assert pend.get() == "ACK"
        # Now in sync with child.
        ptime = time.time()
        ctime = pend.get()
        print "Time delta: %.8f s." % abs(ptime - ctime)

def writer_process(cend):
    with cend:
        assert cend.get() == "SYN"
        # Now in sync with parent.

if __name__ == "__main__":

The marked code blocks in parent and child are entered quasi-simultaneously. Example output on my test machine (Linux): Time delta: 0.00005388 s. On Windows, time.time()‘s precision is not sufficient to resolve the time delta (and time.clock() is not applicable for comparing times across processes).

gipc API

Spawning child processes

gipc.start_process(target, args=(), kwargs={}, daemon=None, name=None)

Start child process and execute function target(*args, **kwargs). Any existing instance of gipc._GIPCHandle or gipc._GIPCDuplexHandle can be passed to the child process via args and/or kwargs. If any such instance is passed to the child, the corresponding file descriptor is automatically closed in the parent.


Compared to the canonical multiprocessing.Process() constructor, this function

  • returns a gipc._GProcess instance which is compatible with the multiprocessing.Process API.
  • just as well takes the target, arg=(), and kwargs={} arguments.
  • introduces the daemon=None argument.
  • does not accept the group argument (being an artifact from multiprocessing‘s compatibility with threading).
  • starts the process, i.e. a subsequent call to the start() method of the returned object is not needed.
  • target – Function to be called in child. Signature: target(*args, **kwargs).
  • args – Tuple defining positional arguments provided to target.
  • kwargs – Dictionary defining keyword arguments provided to target.
  • name – Forwarded to
  • daemon – Forwarded to multiprocessing.Process.daemon.

gipc._GProcess instance (inherits from multiprocessing.Process and re-implements some of its methods in a gevent-cooperative fashion).

start_process() triggers most of the magic in gipc. Process creation is based on multiprocessing.Process(), i.e. fork() on POSIX-compliant systems and CreateProcess() on Windows.


Please note that in order to provide reliable signal handling in the context of libev, the default disposition (action) is restored for all signals in the child before executing the user-given target function. You can (re)install any signal handler within target. The notable exception is the SIGPIPE signal, whose handler is not reset to its default handler in child processes created by gipc. That is, the SIGPIPE action in children is inherited from the parent. In CPython, the default action for SIGPIPE is SIG_IGN, i.e. the signal is ignored.

Creating a pipe and its handle pair

gipc.pipe(duplex=False, encoder='default', decoder='default')

Create a pipe-based message transport channel and return two corresponding handles for reading and writing data.

Allows for gevent-cooperative transmission of data (any picklable Python object by default). Data can be transmitted between greenlets within one process or across processes (created via start_process()).

  • duplex
    • If False (default), create a unidirectional pipe-based message transport channel and return the corresponding (_GIPCReader, _GIPCWriter) handle pair.
    • If True, create a bidirectional message transport channel (using two pipes internally) and return the corresponding (_GIPCDuplexHandle, _GIPCDuplexHandle) handle pair.
  • encoder – Defines the entity used for data serialization before writing data to the pipe. Must be a callable, None or 'default'. 'default' translates to pickle.dumps (any pickleable Python object can be transmitted in this mode). When setting this to None, no data encoding/serialization is performed (only byte strings can be transmitted in this case, in all other cases a TypeError will be thrown).
  • decoder – Defines the entity used for data deserialization after reading raw data from the pipe. Must be a callable, None or 'default'. 'default' translates to pickle.loads. When setting this to None, no data decoding/deserialization is performed (a raw byte string is returned).

gipc._GIPCHandle and gipc._GIPCDuplexHandle instances are recommended to be used with a context manager as indicated in the following examples:

with pipe() as (r, w):
    do_something(r, w)
reader, writer = pipe()

with reader:
    with writer as w:
with pipe(duplex=True) as (h1, h2):
    assert h2.get() == 1
    assert h1.get() == 2

The transport layer is based on os.pipe() (i.e. CreatePipe() on Windows and pipe() on POSIX-compliant systems).

Handling handles

class gipc.gipc._GIPCHandle

The _GIPCHandle class implements common features of read and write handles. _GIPCHandle instances are created via pipe().


Close underlying file descriptor and de-register handle for further usage. Is called on context exit.

class gipc.gipc._GIPCWriter

Bases: gipc.gipc._GIPCHandle

A _GIPCWriter instance manages the write end of a pipe. It is created via pipe().


Encode object o and write it to the pipe. Block gevent-cooperatively until all data is written. The default encoder is pickle.dumps.

Parameters:o – a Python object that is encodable with the encoder of choice.
class gipc.gipc._GIPCReader

Bases: gipc.gipc._GIPCHandle

A _GIPCReader instance manages the read end of a pipe. It is created via pipe().


Receive, decode and return data from the pipe. Block gevent-cooperatively until data is available or timeout expires. The default decoder is pickle.loads.

Parameters:timeoutNone (default) or a gevent.Timeout instance. The timeout must be started to take effect and is canceled when the first byte of a new message arrives (i.e. providing a timeout does not guarantee that the method completes within the timeout interval).
Returns:a Python object.

Recommended usage for silent timeout control:

with gevent.Timeout(TIME_SECONDS, False) as t:


The timeout control is currently not available on Windows, because Windows can’t apply select() to pipe handles. An OSError is expected to be raised in case you set a timeout.

class gipc.gipc._GIPCDuplexHandle

A _GIPCDuplexHandle instance manages one end of a bidirectional pipe-based message transport created via pipe() with duplex=True. It provides put(), get(), and close() methods which are forwarded to the corresponding methods of gipc._GIPCWriter and gipc._GIPCReader.

Controlling child processes

class gipc.gipc._GProcess

Bases: multiprocessing.process.Process

Compatible with the multiprocessing.Process API.

For cooperativeness with gevent and compatibility with libev, it currently re-implements start(), is_alive(), exitcode on Unix and join() on Windows as well as on Unix.


On Unix, child monitoring is implemented via libev child watchers. To that end, libev installs its own SIGCHLD signal handler. Any call to os.waitpid() would compete with that handler, so it is not recommended to call it in the context of this module. gipc prevents multiprocessing from calling os.waitpid() by monkey-patching multiprocessing.forking.Popen.poll to always return None. Calling gipc._GProcess.join() is not required for cleaning up after zombies (libev does). It just waits until the process has terminated.

Exception types

exception gipc.GIPCError

Is raised upon general errors. All other exception types derive from this one.

exception gipc.GIPCLocked

Is raised upon attempt to close a handle which is currently locked for I/O.

exception gipc.GIPCClosed

Is raised upon operation on closed handle.