HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Pyrlang
Pyrlang
Python2017–2021
Pyrlang / Pyrlang

Pyrlang

Erlang node implemented in Python 3.5+ (Asyncio-based)

Systems & InfrastructureLibraries & SDKs
Explore on GitHubRead Hacker News discussions
3Distinct people
4Mentions
0Explicit recommenders
639GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Erlang node implemented in Python 3.5+ (Asyncio-based)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year4 dated mentions

Observed mentions: 2017-11-13 16:26:09 UTC to 2021-10-23 14:38:50 UTC.

0122017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC110
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202

What Hacker News says

4 sources
linkdd·Oct 23, 2021
> Leaving the Erlang ecosystem (e.g. shelling out) always felt painful - https://hexdocs.pm/rambo/Rambo.html - https://hexdocs.pm/elixir/1.12/Port.html - https://github.com/Pyrlang/Pyrlang - https://github.com/goerlang/node - https://erlang.org/doc/apps/erl_interface/ei_users_guide.html - https://erlang.org/doc/tutorial/nif.html > Integrating with Kubernetes was painful - https://hexdocs.pm/libcluster/readme.html - https://hexdocs.pm/k8s/usage.html > OTP has its own ways of doing everything and they are often counter to general best practices (e.g. doing hot releases instead of rolling new containers) Now this is opinionated. Hot releases are used mostly if you want to upgrade your drone's software while it's flying. Surely you don't want it to crash? Or if you're a telecom company (like the creator of Erlang), you don't
Read the rest
want an upgrade to kill the on-going communications. Same for a MMO, you don't want an upgrade to disconnect your players. Docker/Kubernetes is not "general best practices". It's only one way out of many. And if you don't need the use cases above, you can put your application in a Docker container and restart it for upgrades, this is how 90% of Elixir/Phoenix webapps are deployed. > One of the neat things about OTP is that you can migrate processes between nodes that are connected in a mesh network. The documentation is really light on how to do this. - https://hexdocs.pm/horde/ - https://hexdocs.pm/highlander/Highlander.html#content - https://github.com/ringling/distro > The only language that comes close to Elixir for me is Rust How? They solve completely different problems. Could you explain?
In Adopting Erlang
linkdd·Apr 10, 2021
> it looks esoteric and interesting. Esoteric maybe, interesting definitely, mainly because: Elixir compiles to Erlang bytecode, executed by the BEAM (the Erlang VM). The BEAM provides an implementation of the Actor Model, and Erlang/Elixir embed that model in their syntax. Erlang's processes are actors, and they can send messages to each other, even if they are not on the same node, this is totally transparent. On top of that, the OTP framework provides abstractions like: - Supervisor: to handle failure of your processes (actors) - Application: what you would call today a "microservice" - GenServer: to provide RPC to the rest of your application - Mnesia: to provide a replicated database to your application - and many more An Erlang/Elixir node runs multiple applications, and they can talk to each other, making your applicati
Read the rest
ons aware of their distributed aspect (which enables complex logic that would not easily be done in another language). Also *hot code reloading*. Whenever you call a function from another module, the BEAM will try to load the most recent version of that module, so you don't need to restart your application (this is not a very common use case, but you don't want to shutdown your flying drone during an upgrade, do you?). Therefore, every function is "async", and every function call (to another module) have an implicit "await". > let's say Erlang/Elixir -- it's super-duper great At that point, it's not an hypothesis anymore to me :) And I did not talk about pattern matching... > could we not just 'bolt on' a new language? > maybe create a typescript-for-erlang? > maybe it already exists and it's called go/rust/etc. Typescript/Javascript async model (Promises and the NodeJS event loop) does not translate well to the actor model. Go & Rust are faaaaaaaaaar behind in term of distributed computing. Maybe because it's not their target? Erlang provides an interface to build nodes without the BEAM, that can still talk with BEAM nodes: - C/C++: https://erlang.org/doc/apps/erl_interface/ei_users_guide.html - Java: https://erlang.org/doc/apps/jinterface/jinterface_users_guide.html - Python: https://github.com/Pyrlang/Pyrlang But it's nowhere near perfect IMHO.
In Ask HN: Is Elixir Still Relevant?
dqv·May 6, 2018
I don't think it's heavy language lock in at all. If I need to do something in Python, I have options like pyrlang[0] and rabbitmq[1]. In fact, parsing in Elixir is not nearly as mature as what is provided in Python. I need to parse emails. Python has `email.parser` which is perfect for my use case. I can easily use Pyrlang to do this. But Elixir is still much better at being an email client (or many email clients). The end result is an email client in Elixir that uses Python to parse the emails. When I started with Elixir, my goal was to use it as much as possible, but delegate as soon as the task is better handled in another language. [0]:https://github.com/esl/Pyrlang [1]:https://www.rabbitmq.com/
In The Erlang Runtime System

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.