Lightweight in-process concurrent programming
C Python C++ Batchfile Assembly Shell
Latest commit 1a23cf9 Feb 2, 2017 @snaury snaury Stop using trashcan api
Failed to load latest commit information.
appveyor Fix running pip on Python 2.6 Jun 12, 2016
benchmarks Remove unuseful while loop in benchmarks Jan 24, 2015
doc Update greenlet.txt Sep 11, 2015
platform Use x instead of r for aarch64 register names Sep 7, 2016
tests Try to fix spurious thread test failures May 16, 2015
.gitignore Script for building manylinux wheels Apr 2, 2016
.travis.yml Build with Python 3.6 on travis and appveyor Jan 6, 2017
AUTHORS Add Fredrik Fornwall to AUTHORS Sep 7, 2016
LICENSE add copyright holders Dec 22, 2011
LICENSE.PSF Attempt to clarify greenlet license Sep 1, 2011 Update Jun 12, 2016
NEWS Stop using trashcan api Feb 1, 2017
README.rst Convert readthedocs link for their .org -> .io migration for hosted p… May 29, 2016
appveyor.yml Stop using trashcan api Feb 1, 2017 Don't symlink libraries unless inplace build is requested Jun 25, 2014
dev-requirements.txt Start building greenlet with appveyor Jun 11, 2016
greenlet.c Stop using trashcan api Feb 1, 2017
greenlet.h Stop using trashcan api Feb 1, 2017
make-manifest update make-manifest and Jan 7, 2014
make-manylinux Use a shared volume label for SELinux compatibility (fixes #108) Sep 9, 2016
make-win-release Build 3.5 binaries on Windows Sep 21, 2015 Don't symlink libraries unless inplace build is requested Jun 25, 2014 Catch unit-test errors in Sep 24, 2014
setup.cfg Add gztar to sdist formats Aug 29, 2015 Stop using trashcan api Feb 1, 2017
setup_switch_x64_masm.cmd make the greenlet module work on x64 windows Dec 18, 2011
slp_platformselect.h arm32: Make it work on iOS May 31, 2015
tox.ini add testenv:docs, which tests "make html" in doc directory Jan 26, 2012


The greenlet package is a spin-off of Stackless, a version of CPython that supports micro-threads called "tasklets". Tasklets run pseudo-concurrently (typically in a single or a few OS-level threads) and are synchronized with data exchanges on "channels".

A "greenlet", on the other hand, is a still more primitive notion of micro-thread with no implicit scheduling; coroutines, in other words. This is useful when you want to control exactly when your code runs. You can build custom scheduled micro-threads on top of greenlet; however, it seems that greenlets are useful on their own as a way to make advanced control flow structures. For example, we can recreate generators; the difference with Python's own generators is that our generators can call nested functions and the nested functions can yield values too. Additionally, you don't need a "yield" keyword. See the example in tests/

Greenlets are provided as a C extension module for the regular unmodified interpreter.

Greenlets are lightweight coroutines for in-process concurrent programming.

Who is using Greenlet?

There are several libraries that use Greenlet as a more flexible alternative to Python's built in coroutine support:

Getting Greenlet

The easiest way to get Greenlet is to install it with pip or easy_install:

pip install greenlet
easy_install greenlet

Source code archives and windows installers are available on the python package index at

The source code repository is hosted on github:

Documentation is available on