py_interface | Python integration : a Python program

by tomas-abrahamsson Python Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | py_interface Summary

py_interface is a Python library typically used in Web Services applications. py_interface has no bugs, it has no vulnerabilities and it has low support. However py_interface build file is not available and it has a Non-SPDX License. You can download it from GitHub.

The py_interface provides the possibility to create a node that may be used for communication with other Erlang nodes. Some characteristics: * The Python nodes are hidden, like the Java nodes * 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) * The Python node does currently not do: - linking - tracing * 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. * The Python node is a single threaded callback-driven process. * The Python node is released under LGPL, see the file COPYING.LIB. * Work originally begain with Erlang R7 and Python 1.5 * It was recently tested with Erlang 19.2 as well as R15B03 and Python 3.5 * The source of information for this Python node has been the files ‘distribution_handshake.txt’ and ‘erl_ext_dist.txt’ together with the Java node source files, the ‘net_kernel.erl’ and the ‘dist_util.erl’ files in the Erlang source code distribution. Nowadays, this is all documented here:

Support

Quality

Security

License

Reuse

Support

py_interface has a low active ecosystem.

It has 54 star(s) with 7 fork(s). There are 12 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 3 have been closed. On average issues are closed in 270 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of py_interface is current.

Quality

py_interface has no bugs reported.

Security

py_interface has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

py_interface has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

py_interface releases are not available. You will need to build from source code and install.

py_interface has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed py_interface and discovered the below as its top functions. This is intended to give you an instant insight into py_interface implemented functionality, and help decide if they suit your requirements.

Pass a control message to a remote node
Interns the ID of the specified PID
Unpack an ErlMapKey object
Send an RPC
Sends a message to a destination
Send msg to destination
The PID of this process
Send RPC to the receiver
Find the mbox with the given name
Respond to an epmd response
Send Alive2 request
Align a node name
Push a read event
Pushes an exception handler
Tries to connect to an EPMD server
Initiate connection
Process received messages
Debugging output
Logs a debug message
Creates a new mbox
Handle incoming messages
Pops an exception handler
Sends a control message
Send Alive request
Start TCP connection
Pushes a read event
Queues a write event

Get all kandi verified functions for this library.

py_interface Key Features

No Key Features are available at this moment for py_interface.

py_interface Examples and Code Snippets

No Code Snippets are available at this moment for py_interface.

Community Discussions

Trending Discussions on py_interface

Access pybind11 kwargs in C++

Python - importing c++ module interfaces - cannot open shared object file

QUESTION

Access pybind11 kwargs in C++

Asked 2020-Aug-13 at 16:15

I have the following kwargs in python:

...

ANSWER

Answered 2020-Aug-13 at 16:15

You can use py::sequence to access items by indices. Just be sure element exist under the given index:

Source https://stackoverflow.com/questions/63398434

QUESTION

Python - importing c++ module interfaces - cannot open shared object file

Asked 2017-Apr-06 at 14:55

I'm using folder structure like this:

...

ANSWER

Answered 2017-Apr-06 at 14:55

Are you sure . is the directory you're expecting? Note . means current working directory. launcher.py is not in the same directory as lib.so, and so that's what you're seeing. The way you linked things, you have to work in the app dir.

Try using real paths when linking or the path relative to the library, py_interfaces.so. This is something you need to fix in py_interfaces itself.

EDIT:

Here is a SO post about referencing a file relative to the executable/library path.

As mentioned by N.M. n the comments, the correct way to link with a relative path is to provide -rpath with $ORIGIN when linking, making the whole dependency thing more robust.

Source https://stackoverflow.com/questions/43254763

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install py_interface

You can download it from GitHub.
You can use py_interface like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: