Warning
New usages of eventlet are now heavily discouraged! Please read the following.
Eventlet was created almost 18 years ago, at a time where async features were absent from the CPython stdlib. With time eventlet evolved and CPython too, but since several years the maintenance activity of eventlet decreased leading to a growing gap between eventlet and the CPython implementation.
This gap is now too high and can lead you to unexpected side effects and bugs in your applications.
Eventlet now follows a new maintenance policy. Only maintenance for stability and bug fixing will be provided. No new features will be accepted, except those related to the asyncio migration. Usages in new projects are discouraged. Our goal is to plan the retirement of eventlet and to give you ways to move away from eventlet.
If you are looking for a library to manage async network programming, and if you do not yet use eventlet, then, we encourage you to use asyncio, which is the official async library of the CPython stdlib.
If you already use eventlet, we hope to enable migration to asyncio for some use cases; see Migrating off of Eventlet. Only new features related to the migration solution will be accepted.
If you have questions concerning maintenance goals or concerning the migration do not hesitate to open a new issue, we will be happy to answer them.
Eventlet
Eventlet is a concurrent networking library for Python that allows you to change how you run your code, not how you write it.
It uses epoll or libevent for highly scalable non-blocking I/O. Coroutines ensure that the developer uses a blocking style of programming that is similar to threading, but provide the benefits of non-blocking I/O. The event dispatch is implicit, which means you can easily use Eventlet from the Python interpreter, or as a small part of a larger application.
It’s easy to get started using Eventlet, and easy to convert existing applications to use it. Start off by looking at the examples, common design patterns, and the list of basic API primitives.
Getting Eventlet
The easiest way to get Eventlet is to use pip:
pip install -U eventlet
To install latest development version once:
pip install -U https://github.com/eventlet/eventlet/archive/master.zip
Building the Docs Locally
To build a complete set of HTML documentation:
tox -e docs
The built html files can be found in doc/build/html afterward.
Supported Python versions
Python 3.8-3.13 are currently supported.
9 maintainers
Metadata
9 maintainers
Release files for eventlet 0.41.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| eventlet-0.41.2.tar.gz | 566.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| eventlet-0.41.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 930.9 kB
Release files / eventlet-0.41.2.tar.gz
| Download URL | eventlet-0.41.2.tar.gz |
|---|---|
| Size | 566.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
721b86b77fca33a735598292022ac6feef99747bf48f52defdada6b572acd5af
|
|
BLAKE2b-256 checksum How to use checksums |
ebe86a3a23a3b85ed129b21309c6eca873d833855e63879cd72b9dac20d9b76a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 14, 2026.
Transparency logRelease files / eventlet-0.41.2-py3-none-any.whl
| Download URL | eventlet-0.41.2-py3-none-any.whl |
|---|---|
| Size | 364.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6cae50e67fe6ae8bb7013e7fd4d8e0d0d20aeb9b3259b93f023c93eb6749631f
|
|
BLAKE2b-256 checksum How to use checksums |
23759681fa59c4b27d9e34e8be682d2fff3f5be87bf6552477f9a5d395a068c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 14, 2026.
Transparency log
