That's probably a mater of perspective, you and a lot of people seems to be building a REST API splitting functionality into independent services, and is great and a good thing, but it means the architecture needs to have complexity and failures in the right mind/context.
It's not right to bring just twisted to the discussion, I can give you tornado as completely the opposite, it's beautiful and simple and plays great with the multi-process libraries and asyncio, Python 3, etc.
The concurrency models are just different and it's probably nothing wrong with that, single threaded processing using coroutines inside and talking with other processes by message passing using zmq and not rabbit could be monitored with supervisor another great python tool... they are just different tools for different jobs that in fact work in team better that for each own, Python + Erlang.
My point is that is like comparing a mango with a sunfruit, and again there's nothing wrong with the erlang syntax.
Btw I know rabbit it's build on Erlang but again I think it's not a good Erlang example, you could used cowboy as a better OTP builded Erlang application, and again just a mater of perspective.
