Very cool. Just a few days ago, I had noted a proposed spec for a biologically-inspired high-level concurrency model where no user-facing channels/send/recv are required. The user secrets proteins, defines their receptors, and the system handles the rest. Unlike you, I don't have an implementation, but now with GPT 5.6 released it's within reach. The actionable spec prompt is at https://gist.github.com/impredicative/a0dd4ac68cd05e9d3855dc...
Show HN: Runloom – Go-style coroutines for Python free-threaded
31–36 of 36 posts
Re: Show HN: Runloom – Go-style coroutines for Python free-threaded
#32Earlier quoted context omitted.
It might be worth recreating the git history from scratch in a way that excludes the markdown files - I've used Claude Code and OpenAI Codex to do that in the past with git-filter-branch. Lets you preserve the important history but clean out all the junk.
This is a good idea. I'll restore the history in the coming days. Just want to make sure there's nothing embarrassing as claude dumped so many files.
Why would you be embarassed for output by an LLM? You might be overthinking this.
Also, it would be courteous to mention in the readme just how this code came about.
Re: Show HN: Runloom – Go-style coroutines for Python free-threaded
#33[dead]
Re: Show HN: Runloom – Go-style coroutines for Python free-threaded
#34This is an intimidating amount of code! 12,303 lines of C and 244,740 lines of Python, which looks to be a ton of monkeypatching plus huge amounts of test code. Only one commit added all of that, just two hours ago. The published numbers are impressive, but its hard to evaluate how much trust can be put in a project of this complexity at this early stage.
I've restored the git history. This show hn probably would have gone much better if I knew you could add a text section to the link. I had written up a whole post to explain the project and why the code exists. Only for that to get like 3 upvotes and disappear into the void. Then I posted this and it got more attention but had no context since I never planned it.
The project has a few goals:
(1) see how far I can push AI -- this project is extremely complex -- an n:m work-stealing stackful runtime for Python with multiple I/O backends. If I can reasonably get such a project stable fully vibe coded. Then that sells the model to me at least.
(2) scale Python's networking as there is a huge gap between Python and Go. Most people don't think of Python as their first choice for networking. But I love python, i think its extremely elegant. So what if we could add a runtime extension that improved python networking.
That's the work so far at least. It was about 2 - 3 months of testing and the commits now show the history.
Re: Show HN: Runloom – Go-style coroutines for Python free-threaded
#35This is an intimidating amount of code! 12,303 lines of C and 244,740 lines of Python, which looks to be a ton of monkeypatching plus huge amounts of test code. Only one commit added all of that, just two hours ago. The published numbers are impressive, but its hard to evaluate how much trust can be put in a project of this complexity at this early stage.
I've restored the git history. This show hn probably would have gone much better if I knew you could add a text section to the link. I had written up a whole post to explain the project and why the code exists. Only for that to get like 3 upvotes and disappear into the void. Then I posted this and it got more attention but had no context since I never planned it. The project has a few goals: (1) see how far I can pus…
Nice! Having the history makes it easier to evaluate all the work you've put in, this is really impressive.
Re: Show HN: Runloom – Go-style coroutines for Python free-threaded
#36Earlier quoted context omitted.
I've restored the git history. This show hn probably would have gone much better if I knew you could add a text section to the link. I had written up a whole post to explain the project and why the code exists. Only for that to get like 3 upvotes and disappear into the void. Then I posted this and it got more attention but had no context since I never planned it. The project has a few goals: (1) see how far I can pus…
Nice! Having the history makes it easier to evaluate all the work you've put in, this is really impressive.
thanks a lot, thats kind of you to say. Claude definitely deserves a lot of credit too even though its a tool. It would have taken me years to do all that coding.