Hacker News new | ask | show | jobs
by kevingadd 5823 days ago
I pity anyone who has to debug problems caused by monkeypatching the socket module... I wish people would stop trying to solve problems with monkeypatching in python. There are better solutions. Cool idea other than that, though.

Does anyone know of any large-scale projects using this library? It would be interesting to see how it performs in the real world - not needing to use OS threads means that maybe you won't have as much trouble with the GIL, but on the other hand, operations like socket.read() are supposed to release the GIL while they block anyway.
2 comments
cgbystrom 5822 days ago
Well, you can either monkey patch the socket module OR do the callback hell + completely alienate you from the Python ecosystem.

I'm not saying these are perfect solutions. But gevent with greenlet addresses the problem at the right level. Making developers care about asynchronous I/O only when they need it. Not the other way around as with many other async/event based frameworks.

We're actually using it for our real-time web framework Planet (http://www.esn.me) and our cloud-hosted WebSocket service, Beacon (http://beaconpush.com). So far, so good!

link
denik 5823 days ago
Monkey patching is not mandatory. 3rd party modules can be "ported" to gevent manually as well. It's a matter of preference probably. Would like to know what better solutions you have in mind.

not sure if counts as large-scale but omegle.com uses gevent. 9257 users online currently.

link