prxnvt ec7ee8d4ea Engine: a Python cell that keeps only its value keeps its whole cached result ...

When a file is opened, a Python cell falls back to keeping only its value in
four cases: its code is missing from the Python part or the part is damaged
(the xlsx reader), its code is too long for a cell, its kept result is
malformed, or its result is past the adoption budget. The first kept the
values the cell spilled as plain values; the others dropped them, so values
the file showed were lost. All of them now follow one rule, through
Sheet::settle_spill: the anchor and every spilled cell keep their cached
values as plain values, with no live spill range; a cell's own content and
format are never overwritten; and the work is bounded by the spilled values
stored, not by the range. The values move from the spill into the cells, so
nothing is copied. The cut-by-budget test is renamed for what it now checks,
the dropped-result test now expects the values kept, and the adoption warning
and the file-format docs say so.

2026-11-01 13:28:19 -05:00

..

examples

fix: satisfy stricter clippy lints CI's newer stable toolchain catches

2026-10-12 02:52:07 +02:00

src

Engine: a Python cell that keeps only its value keeps its whole cached result

2026-11-01 13:28:19 -05:00

tests/it

Merge main into Python cells as data

2026-11-01 12:00:09 -05:00

Cargo.toml

Enforce workspace Clippy standards and document lint policy

2026-10-28 10:52:53 +00:00