"libev is really easy to embed and that’s what we’re going to do for the next version: put all the dependencies in the release tarball. Hopefully this will reduce the number of build problems people get. This will also remove the number of possible variations of gevent because of different library versions used. There still will be an option to dynamically link against the dependencies, it just won’t be the default."<p>Will this really reduce the number of library version used? I would expect every linux distribution to dynamically link gevent to their existing package of libev.
Interesting, I was just trying to figure out how to install this last night on a Ubuntu Lucid VM. Eventually though I just gave in and installed/used pip. Was ultimately successful, although it seems to be using an old libevent 1.4 even though there is a 2.0 out that it is supposed to be faster.<p>I originally was attracted to gevent after reading about its excellent performance and resource usage. I'd like to use it in concert with nginx to host a django app. I wonder if this is the best choice though? I got it to work, but it seemed a little unnecessarily complex... having to install large dependencies/compile things on the server. Maybe I should just use the wsgi module built into nginx?<p>These packages are so new I'm not confident on the best course of action.
in my experience a lean mean libevent api is the winner. once i need dns or http for size or speed there are more choices than to bog down the event handler. Yes, I understand the benefit of having dns/http/and who knows what in the event handler. once a program needs event handling for multi platform simplicity still the best way to go. i stopped using libevent since the dns/http stuff was added. and in some cases i had to write event handlers from scratch for different oses to have uniformly good acceptable performance.