Python 3.14 compiled to metal – no interpreter
hamza_q_
134 points
100 comments
July 06, 2026
Related Discussions
Found 5 related stories in 1279.5ms across 14,015 title embeddings via pgvector HNSW
- Python 3.15's JIT is now back on track guidoiaquinti · 326 pts · March 17, 2026 · 51% similar
- Python 3.15.0 beta 1 is here GalaxySnail · 12 pts · May 08, 2026 · 47% similar
- Show HN: I built Wool, a lightweight distributed Python runtime bzurak · 13 pts · March 14, 2026 · 43% similar
- Running Python code in a sandbox with MicroPython and WASM pretext · 15 pts · June 06, 2026 · 43% similar
- Running Python code in a sandbox with MicroPython and WASM theanonymousone · 91 pts · June 06, 2026 · 43% similar
Discussion Highlights (17 comments)
ubercore
I hate to be that guy, but... one week old project, clear signs of vibing. I will be shocked if the remaining work listed (cpython test suite) proceeds in any reasonable timeline. This is a pretty hard problem to just solve in a week. EDIT: and man, these kind of comments LLM created comments are really starting to grind my gears as my job slowly turns into reviewing LLM PRs: > Known gaps at the language level are burned down through the ratcheted floors above — the committed floor files, not this README, are the authoritative compatibility baseline.
westurner
How does performance compare to RustPython compiled in a similar way?
cuzezzzbbfofai
Can it run Numpy and Torch?
echoangle
What happens if you call exec/eval? Are they just not available?
leobuskin
A few problems with this Fable's project: 1. It's not Python by any means, it's a subset with its own runtime, its own quirks and nuances; 2. It will be impossible to maintain parity with CPython without AI assistance; 3. It will die the same way as dozens of similar (even non-AI projects) died before, and reasons will be the same: (1) and (2).
iLoveOncall
Can those AI slop projects have a reserved tag on HackerNews? So many in the past few weeks I wouldn't have clicked and wasted my time on if I knew it was just some vibe-coded garbage.
RantyDave
Don't we have Nuitka for this?
getpokedagain
>> The project is under heavy active development Is a pretty oof sentence for a project with one contributor and no users. Just reeks of llm barf with no oversight.
drivebyhooting
Looks like it still uses python object model. You need auto unboxing for good performance.
dr_kretyn
Awesome. Not for this repo specifically; more about the trend. More people are realizing that we have such powerful tools at our disposal and will want to do something awesome, worth while with them. Of course, many will fall off after a week, then more after a month, but some will survive. Knowledge will be spread and some will be winners through adoption. Grit can lead to knowledge, and can lead to awesome stuff.
elzbardico
Seems to be slow as molasses compared to cpython.
bbminner
If AI can find new proofs for well posed math problems, i see no reason why it shouldn't be able to implement a more performant fully featured version of an existing interpreter (eg with JIT and AOT) that emulates python api well and passes all python tests and tests of other projects. It is true that a lot of human effort and thought has been put into squeezing performance out of the existing implementation. It is true that many people have found that getting that last 1% of python test suite to pass turned out to be insurmountably hard. Same is true for math, and yet AI sometimes finds simple solutions that we somehow missed. Maybe there's a simple optimization that was used in an obscure interpreter of a domain specific language that we never heard of. Worth a shot in my mind. If that turns out to be successful, we should ideally find the code that served "as an inspiration" if any. It might make more practical sense to start from CPython and try to optimize that further though. It even has a "not fully fleshed out" JIT already.
xiaodai
it's been tried 10 million times. so yeah
thx67
A couple of other interesting Python compiler projects recently.. https://github.com/Nonannet/copapy uses copy and patch, discussed here https://news.ycombinator.com/item?id=46972392 Single-pass SSA bytecode compiler and threaded-code stack VM for a sandboxed Python subset https://github.com/dylan-sutton-chavez/edge-python
frollogaston
Dynamic typing means you don't know the sizes/offsets of things beforehand. The "compiled to metal" thing still resembles a runtime more than your typical compiled code. Like naively, object would be a struct with a hashmap of property names->values since technically you can alter the keys at runtime, and many values will be pointers to other objects. Idiomatic C or Rust code will have flatter structs. Is it faster than the original interpreter? Maybe if you optimize out the primitives and certain well-known object types, unless you do some more advanced static analysis.
zoom6628
Mojo not good enough?
piloto_ciego
Lol, all the people squawking about how this means nothing and this is a worthless project amuses me. A lot of people just don't see it yet. This is coming for literally everything and it is so exciting. The next decade is going to be awesome.