How to combine Python and Erlang?

Overview of Pyrlang Library, a Python library, that implements Erlang distribution protocol 
21 August 2017   2386

Python is the most popular 2017 programming language, according to the IEEE Spectrum index. An interpreted language, Python has a design philosophy that emphasizes code readability (notably using whitespace indentation to delimit code blocks rather than curly brackets or keywords), and a syntax that allows programmers to express concepts in fewer lines of code than might be used in languages such as C++ or Java. The language provides constructs intended to enable writing clear programs on both a small and large scale.

Erlang is a general-purpose, concurrent, functional programming language, as well as a garbage-collected runtime system. Elixir, one of the most popular "young" programming language, runs on the Erlang virtual machine (BEAM).

How to combine Python and Erlang?

For this purpose, Pyrlang Library will suit. 

Pyrlang is a Python library which implements Erlang distribution protocol and creates an Erlang-compatible node in your Erlang cluster.

You can send and receive messages, spawn “processes” on Python side, which will be addressable from Erlang using familiar Erlang concepts like message sending to process identifiers or registered names. Also same works from Python: you can address Erlang processes, send messages to them, monitor and link with them.

The library is designed to be dropped into existing code base with very few changes required.

Learn more at official website.

PyOxidizer to be Available

Project, allowing  package a Python project in the form of a self-contained executable file is written in Rust and has MPL license
25 June 2019   164

The first release of the PyOxidizer utility is available, which allows you to package a Python project in the form of a self-contained executable file, including the Python interpreter and all the necessary libraries and resources. Such files can run in environments without the Python toolkit installed or regardless of the availability of the required version of Python. PyOxidizer can also generate statically related executables that are not associated with system libraries. The project code is written in the Rust language and is distributed under the MPL (Mozilla Public License) 2.0 license.

The project is based on the same-name module for the Rust language, which allows you to embed a Python interpreter into Rust programs to run Python scripts in them. PyOxidizer has now gone beyond the add-on for Rust and is positioned as a tool available to a wider audience for building and distributing self-contained Python packages. For those who do not need to distribute applications in the form of an executable file, PyOxidizer provides opportunities for generating libraries suitable for linking with any applications for embedding the Python interpreter and the necessary set of extensions in them.

For end users, delivering a project in the form of a single executable file greatly simplifies installation and eliminates the work of selecting dependencies, which is important, for example, for complex Python projects, such as video editors. For application developers, PyOxidizer allows you to save time on organizing the delivery of an application without having to use different tools for building packages for different operating systems.

The use of the proposed builds also has a positive effect on performance - files generated in PyOxidizer run faster than using system Python by eliminating imports and defining basic modules. In PyOxidizer, modules are imported from memory - all built-in modules are immediately loaded into memory and then used without accessing the disk). In tests, application startup time using PyOxidizer is approximately halved.

From already existing similar projects it is possible to note: PyInstaller (unpacks the file into a temporary directory and imports modules from it), py2exe (tied to the Windows platform and requires distribution of several files), py2app (tied to macOS), cx-freeze (requires separate packaging of dependencies ), Shiv and PEX (form a package in zip format and requires Python in the system), Nuitka (compiles the code, not the interpreter embeds), pynsist (tied to Windows), PyRun (proprietary development without explanation of the principles of operation).

At the current stage of development, PyOxidizer has already implemented the main functionality for generating executable files for Windows, macOS and Linux. Of the currently unavailable features, there is a lack of a typical build environment, the impossibility of generating packages in the MSI, DMG and deb / rpm formats, problems with packaging projects that include complex extensions in the C language, and the lack of commands to maintain delivery ("pyoxidizer add" and "pyoxidizer upgrade"), limited support for Terminfo and Readline, lack of support for releases other than Python 3.7, lack of support for resource compression, inability to cross-compile.