[erlang-questions] supervise a python process

Joseph Wayne Norton <>
Fri Feb 11 15:19:44 CET 2011


For Python/Erlang integration, I have had success with the following approaches:

- py_interface
   http://www.lysator.liu.se/~tab/erlang/py_interface/

- Python EBF client
   https://github.com/norton/ubf/blob/master/priv/python/pyebf.py

- Python JSON RPC client
   https://github.com/norton/ubf/blob/master/priv/python/jsonrpc.py

The latter two methods haven't been documented yet.  Though, there is some general UBF documentation in place (http://norton.github.com/ubf/ubf-user-guide.en.html).


On 2011/02/11, at 22:39, Gleb Peregud wrote:

> If you don't need some blazing performance and need a quick solution, then
> ErlPort is a great choice. So +1
> On 11 Feb 2011 13:20, "Dmitry Vasiliev" <> wrote:
>> 11.02.2011 14:11, Roberto Ostinelli пишет:
>>> i need to integrate existing python code with a SOA erlang layer, which
>>> provides some distribution facilities.
>>> 
>>> i'm thinking to use BERT to enable communication between the erlang layer
>>> and python. the main point to not use ports is that, afaik, that if a
> python
>>> port crashes the whole erlang VM goes down, and the point of using erlang
>>> supervisors to provide fault-tolerancy gets lost.
>> 
>> It's just not true. Only the process which created the port (the
>> connected process of the port which is linked to the port) is terminates
>> when port is closed. So you can easily use supervisors with ports.
>> 
>> You can try ErlPort (http://erlport.org/) for ports based integration of
>> Erlang and Python.
>> 
>> --
>> Dmitry Vasiliev <dima at hlabs.org>
>> http://hlabs.org
>> http://twitter.com/hdima
>> 
>> ________________________________________________________________
>> erlang-questions (at) erlang.org mailing list.
>> See http://www.erlang.org/faq.html
>> To unsubscribe; mailto:
>> 

Joseph Wayne Norton






More information about the erlang-questions mailing list