What is gipc?
Usage of Python's multiprocessing package in the context of a gevent-powered application may raise various problems and most likely breaks the application in many ways.
gipc (pronunciation "gipsy") is developed with the motivation to solve many of these issues transparently. With gipc, multiprocessing.Process-based child processes can safely be created anywhere within your gevent-powered application. The API of multiprocessing.Process objects is provided in a gevent-cooperative fashion. Furthermore, gipc comes up with a pipe-based transport layer for gevent-cooperative inter-process communication and useful helper constructs. gipc is lightweight and simple to integrate.
What are the boundary conditions?
Currently, gipc is developed against gevent 1.0. It is tested on CPython 2.6 & 2.7 on Linux as well as on Windows. Python 3 will be supported as soon as gevent supports it.
Where are documentation and changelog?
How can the unit tests be run?
If you run into troubles with gipc, it is a good idea to run the unit test suite under your conditions. gipc's unit tests are written for pytest. With gipc/test (included in the release) being the current working directory, I usually run tests like this:
$ py.test -v
How is code audit perfomed?
I use pep8 and pylint. Have a look at audit.sh in the code repository. Unit test code coverage analysis requires coverage and pytest-cov. audit.sh leaves behind a coverage HTML report in the coverage_html directory.