What is gipc? ============= Naive 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 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 tested on CPython 2.6 & 2.7 and developed against gevent 1.0rc2. Where is the documentation? =========================== The API documentation and further details can be found at http://gehrcke.de/gipc. Is gipc stable? =============== Development began in late 2012, so it is far from being mature. However, as of version 0.3.0, I am not aware of any fundamental issue. gipc's basic approach has proven to be reasonable. gipc is developed with a strong focus on reliability and with best intentions in mind. Via extensive unit testing, it has been validated to work reliably in scenarios of low and medium complexity. It is ready to be evaluated in the context of serious projects. Please let me know how gipc performs for you. Where should I download gipc? ============================= Releases are available at `PyPI <http://pypi.python.org/pypi/gipc>`_. The development version can be retrieved from the mercurial repository at `bitbucket <https://bitbucket.org/jgehrcke/gipc>`_. 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 <http://pytest.org>`_. 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 <http://pypi.python.org/pypi/pep8>`_ and `pylint <http://pypi.python.org/pypi/pylint>`_. Have a look at ``audit.sh`` in the code repository. Unit test code coverage analysis requires `coverage <http://pypi.python.org/pypi/coverage>`_ and `pytest-cov <http://pypi.python.org/pypi/pytest-cov>`_. ``audit.sh`` leaves behind a coverage HTML report in the ``coverage_html`` directory. Contact & Help ============== Your feedback and questions are highly appreciated. For now, please contact me via mail at firstname.lastname@example.org or use the `Bitbucket issue tracker <https://bitbucket.org/jgehrcke/gipc/issues>`_. Author & license ================ ``gipc`` is written and maintained by `Jan-Philip Gehrcke <http://gehrcke.de>`_. It is licensed under the `Apache License 2.0 <http://www.apache.org/licenses/LICENSE-2.0.txt>`_.