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.8.7 released — commissions are now booked once per order the way TradingView…
Commission is booked per order, not per fill leg: a reversal's closing and opening legs share one pooled fee, rounded once and split in quantity proportion — applies to strategy.commission.percent, cash_per_order and…
Read more →PyneComp v6.0.56 — v4 and v5 scripts that used to come back broken now convert cleanly:…
Converting a Pine v4 script that assigns a number to a bool variable (var bool flag = 0, then flag := 1) no longer produces a script that fails with a type error — the numbers are converted to true/false the way v4 read…
Read more →PyneCore v6.8.6 released — TradingView's fill prices, average entry price and math.round…
Filled prices are booked on the symbol's tick grid, the form TradingView stores them in - strategy.position_avg_price is the accumulated cost divided by the position size, re-derived on every fill - math.round matches…
Read more →PyneComp v6.0.55 — converting older and library-heavy scripts now produces code that…
Converting a Pine v4 strategy that passed 1 / 0 as the entry direction turned every short into a long. Numeric literals now convert too — 0 becomes strategy.short, anything else strategy.long. - label.all.size() and the…
Read more →PyneCore v6.8.5 released — entries and exits that happen inside a bar now behave the way…
A strategy.exit bracket its own entry activates mid-bar now fills on that same bar: profit=, loss= and trail_points= offsets are resolved at the fill instead of at the next bar's open (#76) - A trailing leg armed…
Read more →PyneCore v6.8.4 released — computed ta lengths now truncate exactly like TradingView,…
A computed length such as R / 8 is now truncated where an integer is required, matching TradingView: ta.cog, ta.highest, ta.linreg, ta.lowest, ta.pivothigh, ta.pivotlow, ta.sma and ta.valuewhen were affected, and ta.sma…
Read more →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 →