I have just released gipc 0.6.0 introducing support for Python 3. This release has been motivated by gevent 1.1 being just around the corner, which will also introduce Python 3 support.
Changes under the hood
The new gipc version has been verified to work on CPython 2.6.9, 2.7.10, 3.3.6, and 3.4.3. Python 3.4 support required significant changes under the hood: internally, gipc uses
multiprocessing.Process, whose implementation drastically changed from Python 3.3 to 3.4. Most notably, on Windows, the arguments to the hard-coded
CreateProcess() system call were changed, preventing automatic inheritance of file descriptors. Hence, implementation of a new approach for file descriptor transferral between processes was required for supporting Python 3.4 as well as future Python versions. Reassuringly, the unit test suite required close-to-zero adjustments.
The docs got a fresh look
I have used this opportunity to amend the documentation: it now has a fresh look based on a brutally modified RTD theme. This provides a much better reading experience as well as great support for narrow screens (i.e. mobile support). I hope you like it: https://gehrcke.de/gipc
Who’s using gipc?
I have searched the web a bit for finding interesting use cases. These great projects use gipc:
Are you successfully applying gipc in production? That is always great to hear, so please drop me a line!
As usual, the release is available via PyPI (https://pypi.python.org/pypi/gipc). Please visit https://gehrcke.de/gipc for finding API documentation, code examples, installation notes, and further in-depth information.
I just released gipc 0.5.0. It contains a backwards-incompatible change: the SIGPIPE signal action is not automatically reset to the default action anymore in child processes. This will hopefully satisfy developers expecting the SIGPIPE signal to be ignored, resulting in a proper Python exception when attempting to write to a pipe that has been closed on the read end (if interested, you can follow the related discussion here). Furthermore, this release improves the performance when sending large messages through gipc pipes on Linux. This release also introduces workarounds for two corner case issues present in Mac OS X and FreeBSD.
This is the full changelog:
- Improve large message throughput on Linux (see issue #13).
- Work around read(2) system call flaw on Mac OS X (see issue #13).
- Work around signal.NSIG-related problem on FreeBSD (see issue #10).
- Do not alter SIGPIPE action during child bootstrap (breaking change, see issue #12).
Thanks to Dustin Oprea, bra, John Ricklefs, Heungsub Lee, Miguel Turner, and Alex Besogonov for contributing. As usual, the release is available via PyPI (https://pypi.python.org/pypi/gipc). The documentation and further detail are available at http://gehrcke.de/gipc.
I just released gipc 0.4.0. It plays well together with the recently released final version of gevent 1.0, resolves some minor issues, introduces a convenient interface for custom data encoding and decoding when using pipes, and significantly increases the data transmission bandwidth when sending large messages. Full changelog:
- Implement data (de)serialization pipe API (allowing for raw byte transmission and for custom encoders/decoders).
- Restore default signal disposition in child wrapper for all signals (see Bitbucket issue #7).
- Fix DeprecationWarning related to _PairContext class (see Bitbucket issue #5).
- Significantly improve large message write performance by using Python’s buffer interface.
- Require gevent 1.0 final release version via setup.py.
Thanks to Jonathan Kamens, John Porter, and Ivan Smirnov for contributing. As usual, the release version is available via PyPI (https://pypi.python.org/pypi/gipc). Further details and documentation are available at http://gehrcke.de/gipc.