GeventMP - Gevent Multiprocessing Extension
Problem
Due to internal implementation, multiprocessing (MP) is unsafe to use with Gevent even when monkey-patched. Namely, the use of OS semaphore primitives and inter-process IO in MP will cause the main loop to stall/deadlock/block (specific issue depends on the version of CPython).
Solution
GeventMP (Gee-vent Em-Pee) is a gevent multiprocessing extension plugin for the monkey-patching subsystem. As with the rest of the monkey patch subsystem the process is fairly clear:
Identify all places where blocking occurs and where it may stall the loop.
If blocking occurs on a file descriptor (FD), try to convert the file descriptor from blocking to non-blocking (sockets/pipes/fifos, sometimes even files where, rarely, appropriate) and replace blocking IO functions with their gevent non-blocking equivalents.
If blocking occurs in a Python/OS primitive that does not support non-blocking access and thus cannot be geventized, wrap all blocking access to that primitive with native thread-pool-based wrappers and call it a day (while fully understanding that primitive access latency will increase and raw performance may suffer as a result).
If you are really brave and have lots of free time on your hands, completely replace a standard blocking Python non-FD-based primitive with implementation based on an FD-based OS primitive (e.g. POSIX semaphore => Linux eventfd-based semaphore for kernels > 2.6.30).
Due to launching of separate processes in MP, figure out how, when, and whether to monkey-patch spawned/forked children and grandchildren.
Installation
The package is hosted on PyPi.
For stable version:
pip install geventmp
For unstable version:
pip install --pre geventmp
Once installed, GeventMP will activate by default in the below stanza.
from gevent.monkey import patch_all
patch_all()
If you would like GeventMP to not activate by default, either do not install it or explicitly disable it:
from gevent.monkey import patch_all
patch_all(geventmp=False)
That’s it - there are no other flags, settings, properties or config values so far.
Supported Platforms
Linux and Darwin.
CPython 3.11, 3.12, 3.13, 3.14, 3.15
TODO
Monkey patch Windows to the extent possible.
Lots of applications use Billiard for multiprocessing instead of stock Python package. Consider monkey patching Billiard if detected.
Contact Us
Post feedback and issues on the Bug Tracker, Gitter, and Twitter (@karelleninc).
Metadata
Release files for geventmp 0.0.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| geventmp-0.0.12.tar.gz | 17.3 kB | Without provenance | Details for geventmp-0.0.12.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| geventmp-0.0.12-py3-none-any.whl | Python 3 | none | any | Details for geventmp-0.0.12-py3-none-any.whl |
Total release size: 39.6 kB
Release files / geventmp-0.0.12.tar.gz
| Download URL | geventmp-0.0.12.tar.gz |
|---|---|
| Size | 17.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7b4f89f4135d25f864e258d95049c837a8d22e25e28657a6f442d24d8629c312
|
|
BLAKE2b-256 checksum How to use checksums |
f7267d6e7c377506dc8ce61c8150de87fd60cba711a82bb222a04d1a2dc7e7a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / geventmp-0.0.12-py3-none-any.whl
| Download URL | geventmp-0.0.12-py3-none-any.whl |
|---|---|
| Size | 22.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e6219302629a528468435ded4efb792c45f208778b11dcbf5d4e5c159cedbaae
|
|
BLAKE2b-256 checksum How to use checksums |
90d97452ade735dadbcbaf08396b09b50e090d95e164de17549fcf758941f724
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for geventmp 0.0.12
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.