Dev Updates

Development in the open. PyneCore and PyneComp releases land here as they happen — what got fixed, what got added, and now and then what we got wrong — along with progress on work that is not finished yet. Synced directly from our Discord dev-updates channel.

PyneCore’s full changelog lives on GitHub; PyneComp’s progress you will find here and nowhere else. More granular and more technical than News — this is the engineering log, not the announcements.

PyneCore v6.4.4 — correctness fixes

Partial take-profit exits no longer silently collide (multi-TP strategies) - strategy.cancel() aligned with TV semantics - request.security() safety: locked shared memory, strategy-state guards, tuple-unpack defaults -…

Read more →

PyneCore v6.4.3 — a quick patch release.

Fixes a regression where compiled scripts couldn't be run standalone (python script.py data.csv) on 6.4.2 — the @pyne import-hook check was too loose and accidentally transformed the standalone runner itself, surfacing…

Read more →

PyneComp 6.0.31 — switch codegen fix

Pine switch blocks now compile reliably regardless of how the case targets are written — literals, dotted enum members, and bare-identifier constants all produce valid Python output (if/elif/else).

Read more →

Plugin system – work in progress

If you're curious about what we're working on, feel free to follow the plugin-system branch on GitHub — you can watch the plugin system take shape in real time. Not final yet, but if you want to stay ahead or start…

Read more →

request.security()` — Work in Progress

A highly requested feature is now in active development. Each security context runs as its own OS process with a separate Python interpreter, so there's no global state collision and multi-core parallelism comes for…

Read more →