The Py-Interface is a python-implementation of an Erlang node.
The py_interface provides the possibility to create a node that may be used
for communication with other Erlang nodes.
Some characteristics:
o The Python nodes are hidden, like the Java nodes
o The Python node supports
- registering the Python node in the epmd
- sending and receiving message
- executing remote procedure calls (the rpc:call(M,F,A) mechanism)
o The Python node does currently not do:
- linking
- tracing
o The Python node translates Erlang types to Python types as far as there is a
reasonable Python counterpart. If there is not, then a class is used.
o The Python node is a single threaded callback-driven process.
o The Python node runs on Python 2.5 and Erlang R12. It may well still work
with older version of both Python and Erlang. Development started on
Python 1.5 and Erlang R7.
WWW: http://www.lysator.liu.se/~tab/erlang/py_interface/
===> The following configuration options are available for py27-interface-2.2_1:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
Convert Python ports to FLAVORS.
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
(Only the first 15 lines of the commit message are shown above )
Upgrade to version 1.0.
Now devel/py_otp_interface and devel/py-interface are pretty much the same.
PR: ports/148842
Approved by: maintainer timeout (15 days)
