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.
PyneComp v6.0.54 — scripts that TradingView runs without complaint now compile and run…
A type whose field is declared var or varip produced a script that crashed on startup with a message about persistent variables; such scripts now run, and the variable holding the object keeps its own varip behaviour. -…
Read more →PyneCore v6.8.3 released — nine measured TradingView defects, one measured performance…
Float-to-bool conversion uses Pine's own 1e-10 tolerance, so arithmetic residue like 2.4e-15 no longer fires signals TradingView never draws — if, while, ?:, and, or, not and the explicit bool() cast all agree now. -…
Read more →PyneComp v6.0.53 — converting older Pine scripts (v1–v5) is noticeably more reliable:…
A script that declares a type and a function under the same name no longer converts into code referring to a class that doesn't exist. - A user-type field whose default reads a built-in (close, time, …) now takes its…
Read more →PyneComp v6.0.52 — converted scripts now come back looking like the script you gave it,…
Converting a library that used export type or export enum produced a script that would not compile — TradingView's own published ZigZag/7 library was one of them - Trailing spaces inside a multi-line text literal are…
Read more →PyneCore v6.8.2 released — a strategy's declared account currency is now actually…
Account-currency conversion at the cash-flow level — each amount converts at the rate of the bar it is booked on, so a trade's profit is gross at the exit rate minus each fee at its own bar's rate; run-up and draw-down…
Read more →PyneComp v6.0.50 — legacy Pine conversion fidelity: forward references, eager evaluation…
Forward-referenced series now compile — a legacy up = ... down[1] ... reading a variable declared on a later line — and self-referencing declarations are hoisted the same way - A variable named after a built-in…
Read more →PyneCore v6.8.1 released — a release about scripts that used to stop dead: most of these…
An na array index no longer halts array.get, set, remove, insert, slice, fill, percentrank, max, min or the percentile functions — TradingView's measured answers are returned instead - A float index, from a division or…
Read more →PyneCore v6.8.0 released — most of the ta.* rolling machines, the math.sum accumulator,…
Pine's tolerant float comparison (absolute 1e-10 at every magnitude) now applies to comparison operators in Pyne code and to the builtins measured to compare tolerantly - OHLCV v2 stores the symbol's tick grid in the…
Read more →PyneComp v6.0.49 — Compile error line numbers now point at the original source, and…
Errors from converted (pre-v6) sources now report line numbers of the original file via a new conversion line_map stage - Converter diagnostic messages are kept consistent with the remapped exception line numbers -…
Read more →PyneComp v6.0.48 — legacy v3 migration, const preservation, and a series of parser…
Import aliases no longer collide with same-named user variables or functions — separate namespaces - A user function may claim a built-in type name (line(...), label(...), int, float, …) - An exported function and a…
Read more →