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.10.0 released — backtests with request.security got much faster, plus…
Same-timeframe request.security contexts run their whole history as one batch round - lookahead_on higher-timeframe contexts are batched too, with a lazily streamed plan (lower memory, flat throughput on long charts) -…
Read more →PyneCore v6.9.4 released — scripts can now declare their own timeframe in indicator(),…
Script-level timeframe / timeframe_gaps in indicator(): the script runs once per completed period aggregated from the chart feed, with na or forward-filled values on the other chart bars. No higher-timeframe value is…
Read more →PyneCore v6.9.3 released — dependent request.security() expressions are now synchronized…
A security expression reading another security call's result now sees the peer's value for the correct bar — scripts like request.security(sym, "M", ta.sma(monthlyRsi, n)) no longer diverge. One pairing rule everywhere:…
Read more →PyneComp v6.0.67 — several converter fixes for correctness, mostly around edge cases in…
array.sort and array.sort_indices calls using the sort_field parameter were rejected as invalid — they now work correctly. - Converting a script with a nested ?: ternary containing na could produce broken, unparseable…
Read more →PyneCore v6.9.2 released — the two reported regressions are fixed: na at an integer…
na passed to an int-typed argument raised TypeError instead of answering na at 20 slots — every table dimension and cell coordinate, plus str.replace and str.substring; each now substitutes the integer TradingView…
Read more →PyneComp v6.0.66 — converting an older Pine script now keeps the three-state bool…
Converting a v1–v5 script that let a bool hold na no longer collapses it to plain false — the converted script keeps the same three states the original ran with. - A bool-typed function parameter (e.g. f(simple bool…
Read more →PyneCore v6.9.0 released — Pine int is now a static type over a double-only runtime,…
Every int-typed value travels as an integral float; na(int) is a plain nan, truncation happens at the consuming slot, storage keeps the value (array.new_int(1, 7 / 4) holds 1.75) - Static Pine type inference stamps the…
Read more →PyneComp v6.0.65 — a script that uses a numeric ternary as a condition, like if a and…
Converting or compiling a Pine script where a numeric ? : expression with an na branch is used inside an if condition failed with an internal error (HTTP 400 from the API). It now converts exactly the way TradingView…
Read more →PyneComp v6.0.64 — seven fixes for scripts that used to convert or compile into Python…
A Pine v5 script dividing two integer constants (10 / 3) kept Pine 5's truncating integer result instead of silently turning into a decimal one after conversion — this changed values wherever a script compared against…
Read more →PyneCore v6.8.14 released — twelve TradingView-parity fixes across the strategy engine,…
Same-instant reversals are booked long side first when both entry orders waited in the book together; a calc_on_order_fills-issued leg keeps its chronological order - pyramiding is judged when strategy.entry runs,…
Read more →