Compatibility

Erlang/OTP

Status

29

Supported, tested (29.1.2)

28

Supported, tested (28.4.1)

27

Supported, tested (27.3.4.19)

26

Supported, tested (26.2.5.21)

25

Supported, tested (25.3.2.21)

24 and older

Not supported

Python 3.11 or newer is required. Every release in the table runs the full interop test suite against Pyrlang: real Erlang nodes talking to Pyrlang over the network, including mixed clusters of an old and a new release. Pyrlang depends on Term (pyrlang-term) for the External Term Format; its native (Rust) codec is used when installed, otherwise its pure-Python one.

Distribution features

“Since” is the Erlang/OTP release that introduced the feature.

Feature

Since

Pyrlang

Handshake version 6 ('N' messages, 64-bit flags, 32-bit creation)

23

Yes, the only version spoken

Flags mandatory in OTP 25 and 26 (DFLAG_V4_NC, DFLAG_UNLINK_ID, …)

25/26

Yes

Messages by pid or registered name (SEND, REG_SEND, SEND_SENDER)

— / 21

Yes

Links, link protocol with UNLINK_ID / UNLINK_ID_ACK

23.3

Yes

Monitors (MONITOR_P, DEMONITOR_P, MONITOR_P_EXIT)

—

Yes

Exit signals with the reason as payload (DFLAG_EXIT_PAYLOAD)

22

Yes

Distribution header, atom cache, fragmented messages

22

Yes; received atom cache entries are used, none are sent

Process aliases (ALIAS_SEND)

24

Yes

Alternate action signals (ALTACT_SIG_SEND)

28

Yes; message priority is not kept

Spawn requests: rpc:call, erpc, spawn(Node, M, F, A) into Python

23

Yes (Node.register_spawnable); Python cannot spawn on Erlang nodes

Native records (RECORD_EXT)

29

Yes

Dynamic node names (-name undefined)

23

As the connecting node only

Distribution without EPMD

23

Yes (Node(epmd=False), Node.connect)

Net ticks (net_ticktime)

—

Yes

Trace tokens (*_TT messages)

—

Accepted; the token is dropped

trap_exit

—

No

Flow control (a slow receiver holds back the sender, both ways)

—

Yes (dist_buf_busy_limit, recv_backlog_*)

Every term type that an Erlang/OTP 29 node sends by default can be decoded and encoded, including V4 pids, ports and references, bitstrings, export funs and native records.

Where Pyrlang knowingly behaves differently from an Erlang node, Known differences lists it.