Python is a terribly structured language, full of atrocities like unicode handling, decorators/metaclasses, object system, crippled lambda, braindead "functional" style, idiotic module system (hot code updates yay! oh no it doesn't really work!)
It started out as a Christmas hack and it hasn't really evolved much from then on. The same crap in the core, just more sugar on top. A language aimed at the lowest common denominator, designed to make you think "programming is easy!" but ill-suited to solving any sort of hard problem in a graceful fashion.
Why would anyone want _any_ of that on the Erlang VM?
the Christmas joke starts from: http://python-history.blogspot.com/2009/01/brief-timeline-of... and https://www.python.org/doc/essays/foreword/
So it really surprises me and stuff.
Language level integrated and robust process management/OTP features really are great; you only need to look at something like twisted to see that Python is not a perfect fit for managing this stuff and I'll play with other languages (probably Elixir right now) to see what I can learn.
Maybe the original poster is missing the point that having Python ideas added to a functional language would help? Or maybe I should just learn functional programming properly!
Personally I don't see the need of use every tool in the same way, there is nothing wrong with the erlang syntax.
Only by people who see the world as black and white. There is absolutely nothing wrong with case.
All the @public at the end of the function headers really hurt the eye.
I think there's a reason 90%+ of the languages has either it above the declaration of at the beginning of the line.
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.