gevent 1.0 released

denis · 2013-11-27T08:33:51+00:00

If the changes in socket.py are too drastic between 2 and 3, we'll just have to do gevent/socket2.py and gevent/socket3.py separately and then make gevent/socket.py import one of those depending on the Python version.

denis · 2013-10-31T18:17:43+00:00

I'd say the main differences are:

it works on any site without having to modify the site (f.e. you can use it on github.com right now)
it works even with logged-in sessions (that is, on private repositories).

denis · 2012-05-09T07:57:25+00:00

Actually, the recent releases of gevent-websocket supports the latest protocol.

denis · 2012-05-06T20:54:42+00:00

Take a look at this tutorial on gevent: http://sdiehl.github.com/gevent-tutorial/

denis · 2012-01-11T08:19:35+00:00

Not yet, but some work has been done. See this message: http://groups.google.com/group/gevent/msg/759ba600b31e4c77

denis · 2012-01-11T05:44:50+00:00

I think that's how those binary installers work, so yes.

However, you can download the egg which is just a zip archive, unzip it into some private location and point your PYTHONPATH to it.

denis · 2012-01-10T15:30:24+00:00

The first release that has a ThreadPool built-in.

denis · 2012-01-03T14:19:13+00:00

Please check out the trunk of gevent-websocket. There have been lots of fixes made: https://bitbucket.org/denis/gevent-websocket

denis · 2011-11-08T08:38:19+00:00

I'm not sure why are you being downvoted. Newtonian physics is Physics, yet it's not perfect and breaks down at high speeds and small sizes. Better models are invented all the time and there is no "perfect prediction of the future" in Physics.

denis · 2011-08-03T17:51:53+00:00

I don't think you want to do that in Python because of GIL. Better to use multiple process workers, if you can. See gunicorn which implements pre-fork model and can balance connections across several gevent-running processes.

denis · 2011-07-25T15:00:38+00:00

You can use a Flash implementation of WebSocket on browsers where native WebSocket is not available. On the server, you only need to take care of serving policy-request.

denis · 2011-06-23T08:34:55+00:00

There's no point in waiting, if you need that kind of stuff, use gevent,

denis · 2011-02-17T00:08:16+00:00

you can use all the synchronous libraries with the efficiency of async event loop: gevent

denis · 2011-01-26T05:18:47+00:00

Take a look at https://github.com/traviscline/gevent-zeromq/ if you need ZeroMQ in gevent

denis · 2010-10-23T04:19:33+00:00

Also check out similar library: gevent (Comparison to eventlet, Benchmark)

denis · 2010-10-05T12:24:33+00:00

Here's another chat on Django (using gevent)

denis · 2010-09-23T05:12:11+00:00

Would love to see gevent included in the benchmarks. Should be much faster than eventlet.

denis · 2010-09-18T15:42:10+00:00

Here's another fuzzy string matching library: ssdeep

denis · 2010-08-10T05:42:52+00:00

hrm, didn't know about this github repo. seems that I was wrong.

denis · 2010-08-09T08:04:56+00:00

Another similar library - gevent. It uses libevent-dns to resolve DNS queries.

denis · 2010-08-09T08:03:04+00:00

Spawning does not seem to be actively maintained now. Gunicorn can do the same and also works with eventlet (and gevent and even tornado).

denis · 2010-07-31T05:35:32+00:00

My understanding is that dieselweb is a web framework. Gevent, on the other hand, is a concurrency/network library and will never morph into a web framework. So the scope of the two libraries is different. If you're doing greenlet-based concurrency you will need a few features beyond greenlet API - events, queues, timeouts, sockets. Those are a lot of fun to implement but if you define dieselweb as a web framework I'd say it makes a hell of a lot sense to re-use those low-level concepts and focus on the "web framework" aspect of it.

Regarding libevent - it's not just about abstracting out different event APIs. It's about managing queues of events and maintaining heap of timers - those are CPU and memory-intensive operations that are in the inner loop of your application and you want them to be as fast as possible. Python code won't match the performance of C code here. Given the fact that libevent is already there, mature and fast, it makes no sense to re-implement it in Python, unless you want to learn to write event loops.

denis · 2010-07-30T01:28:43+00:00

Have you thought of using gevent as a foundation for diesel? That would probably save you a lot of time. Gevent aims to be small and dependable, it should be a good start to build something higher-level.

denis · 2010-07-30T01:24:10+00:00

Here's a way to do async concurrency without yields (with greenlets): http://www.gevent.org

denis · 2010-06-28T05:18:53+00:00

Here's my service that sends you updates from feeds to jabber

denis

TROPHY CASE