I don&#x27;t want to be pedantic, but I&#x27;m going to be pedantic (sorry!)<p><pre><code>  You can get Erlang style concurrency out of ... JVM languages (scala&#x2F;akka; quasar)
</code></pre>
This is a little misleading. Yea, akka gives you actors, and on the surface they look similar to erlang processes (they have a receive block, and a ! function call), but I think the more subtle differences are what make erlang interesting, and ultimately really pleasant to work with
1) akka is not preemptive multitasking. actors are multiplexed across a thread pool, so it&#x27;s possible to do blocking IO and screw a bunch of other actors up inadvertently 
2) the whole gc thing that applies across the vm.<p>all sorts of wonderful things fall out of the two properties above, things which you need to work really hard to get in an akka world.<p>as far as foreign interfaces to python, it&#x27;s certainly possible with something like jinterface, but I&#x27;m not really sure what the point would be. generally you leave erlang behind for similar reasons you might leave python behind (things that are cpu bound). jinterface exists because java does a whole bunch of stuff well that erlang falls down at, so they can complement each other nicely. I&#x27;m not sure there are as many of those cases with python.