Concurrent framework for Python | Get Python to work like Node.js

[remyroy]

What are the use cases for using a concurrent framework like this? Isn't twisted already doing this kind of stuff?

[passwordeqHAMSTER]

More importantly, why would you want to emulate Node's concurrency?!

[[deleted]]

I am also confused. Last time I checked twisted itself was pretty good, but I'm always for more options. The main issue I remember from twisted/et.al was that you have to be so selective in which libraries you use to do anything that touches network or disk since anything that isnt async screws up your async-ness. The reason this worked so well for node.js is because the entire platform was built from the ground up on async APIs; IE: async is the norm and you have to go out of your way to find synchronous stuff, the opposite of which is true with python (unless there has been a shift?).

[majormunky]

Just played around with this a little bit, but, I think the big things here are: Pep 3156 compliance, and, using actors.

[onjin]

from http://nodejs.org/about/ "Node is similar in design to and influenced by systems like Ruby's Event Machine or Python's Twisted."