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 ( |
23 |
Yes, the only version spoken |
Flags mandatory in OTP 25 and 26 ( |
25/26 |
Yes |
Messages by pid or registered name ( |
— / 21 |
Yes |
Links, link protocol with |
23.3 |
Yes |
Monitors ( |
— |
Yes |
Exit signals with the reason as payload ( |
22 |
Yes |
Distribution header, atom cache, fragmented messages |
22 |
Yes; received atom cache entries are used, none are sent |
Process aliases ( |
24 |
Yes |
Alternate action signals ( |
28 |
Yes; message priority is not kept |
Spawn requests: |
23 |
Yes ( |
Native records ( |
29 |
Yes |
Dynamic node names ( |
23 |
As the connecting node only |
Distribution without EPMD |
23 |
Yes ( |
Net ticks ( |
— |
Yes |
Trace tokens ( |
— |
Accepted; the token is dropped |
|
— |
No |
Flow control (a slow receiver holds back the sender, both ways) |
— |
Yes ( |
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.