Changelog
Release notes for every shipped version of gopy. Each page is a human-written walkthrough of what landed, why we built it the way we did, and where it lives in the code.
Latest
- v0.12.2 (May 12, 2026). The stdlib import chain drop. Thirty modules vendor real CPython sources, a real regex engine replaces the RE2 shim, and Phase 1 of the object protocol full port lands.
- v0.12.0 (May 8, 2026). The Tier-2 optimizer drop. Trace projector, side-table install path, and the uop dispatch loop land end to end.
- v0.11.0 (May 7, 2026). Adaptive specialization
and
sys.monitoring. - v0.10.2 (May 7, 2026). Parser drop. PEG parser, tokenizer, and AST builder ported 1:1 from CPython.
- v0.10.1 (May 7, 2026). The backlog drop.
All releases
| Version | Date | Theme |
|---|---|---|
| v0.12.2 | 2026-05-12 | Stdlib import chain |
| v0.12.0 | 2026-05-08 | Tier-2 optimizer |
| v0.11.0 | 2026-05-07 | Specialization + monitoring |
| v0.10.2 | 2026-05-07 | Parser drop |
| v0.10.1 | 2026-05-07 | Backlog drop |
| v0.10.0 | 2026-05-06 | GC |
| v0.9.0 | earlier | VM remaining |
| v0.8.0 | earlier | Imports |
| v0.7.0 | earlier | Lifecycle |
| v0.5.5 | earlier | Lexer |
| v0.5.0 | earlier | Compile |
| v0.4.0 | earlier | Number / string |
| v0.3.0 | earlier | Exceptions |
| v0.2.0 | earlier | Types |
| v0.1.0 | earlier | First runnable bytecode |
| v0.0.0 | earlier | Repo scaffold |
Reading guide
If you're new to gopy, start with the latest release notes for the state of the world today, then work backwards for context on how the runtime grew. Every release page follows the same layout:
- Highlights. The two or three things that matter most.
- What's new. The full feature breakdown, grouped by area.
- Why we built it this way. Design rationale and tradeoffs.
- Where it lives. File and package pointers into the repo.
- Compatibility. Anything that changed user-visibly.
- What's next. The handoff to the next release.
Spec references throughout link into the internal design docs
under ~/notes/Spec/1700. Where the spec is private, the prose
captures the same information so the changelog stands alone.