eventlet

The difference is that in co-routine based code (such as concurrence or eventlet) there are no callbacks.

BTW Python has something like it based on the greenlet library (eventlet and gevent libraries are based on).

Better IO handling via something sane like lightweight threads (via an already existing framework like gevent or eventlet).

Python could do green threads (IO-base coroutines) for a long time -- see eventlet, gevent, even Twisted's inlineCallback pattern.

Although this is great and all, what does this do compared to green threads (gevent, eventlet, etc...)?

If you’re running Eventlet on Windows and run into errors, let us know.

Just for the record, eventlet and concurrence are not dead, I even used the latter in production.

Check out Spawning [1], which uses eventlet [2], which uses greenlet [3].

You might want to compare nodejs with PyPY+Tornado or with PyPy+eventlet.

I think Go works like this and Python's eventlet and gevent work that ways.

I've been including Eventlet in a lot of my comments lately, but not because I have any affiliation with it (I don't).

If I'm not mistaken, eventlet/gevent aren't really the direction that Python is heading.

I've been using Akka where it makes sense and while I only played with Quasar, I do have a lot of experience with Gevent and Eventlet in Python and the bit about "synchronous" and "blocking" code being easier (while cheating by patching connections) is bullshit, for one because sometimes it doesn't work creating more problems than it solves and because it doesn't simplify anything of importance.

> the bit about "synchronous" and "blocking" code being easier (while cheating by patching connections) is bullshit [...] People should write asynchronous code throughout the entire call-stack [...] Probably I don't understand because I don't know much about Gevent and Eventlet but for info about Quasar I/O pls.

Currently there’s a large split between folks programming against Twisted, Tornado, Eventlet/Gevent, rolling their own thing, or just writing blocking code and getting crap performance.

Our software stack is built around Linux, Vagrant, Flask, Eventlet, Postgres, RabbitMQ, Git and Chef - but we are not resistant to change as needed.

Our team builds on a modern, open-source software stack which includes Linux, Vagrant, Flask, Eventlet, PostgreSQL, RabbitMQ, ElasticSearch, Graphite, Chef and Git.